summaryrefslogtreecommitdiffstats
path: root/rust/helpers/helpers.c
diff options
context:
space:
mode:
authorJohannes Thumshirn <johannes.thumshirn@wdc.com>2025-05-06 13:27:30 +0200
committerJens Axboe <axboe@kernel.dk>2025-05-06 07:45:59 -0600
commitdb492e24f9b05547ba12b4783f09c9d943cf42fe (patch)
treedd8651cb42fcfe2c1d196e1ac2b5448af0b05972 /rust/helpers/helpers.c
parentf5c84eff634ba003326aa034c414e2a9dcb7c6a7 (diff)
downloadlinux-db492e24f9b05547ba12b4783f09c9d943cf42fe.tar.gz
linux-db492e24f9b05547ba12b4783f09c9d943cf42fe.tar.bz2
linux-db492e24f9b05547ba12b4783f09c9d943cf42fe.zip
block: only update request sector if needed
In case of a ZONE APPEND write, regardless of native ZONE APPEND or the emulation layer in the zone write plugging code, the sector the data got written to by the device needs to be updated in the bio. At the moment, this is done for every native ZONE APPEND write and every request that is flagged with 'BIO_ZONE_WRITE_PLUGGING'. But thus superfluously updates the sector for regular writes to a zoned block device. Check if a bio is a native ZONE APPEND write or if the bio is flagged as 'BIO_EMULATES_ZONE_APPEND', meaning the block layer's zone write plugging code handles the ZONE APPEND and translates it into a regular write and back. Only if one of these two criterion is met, update the sector in the bio upon completion. Signed-off-by: Johannes Thumshirn <johannes.thumshirn@wdc.com> Reviewed-by: Christoph Hellwig <hch@lst.de> Link: https://lore.kernel.org/r/dea089581cb6b777c1cd1500b38ac0b61df4b2d1.1746530748.git.jth@kernel.org Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'rust/helpers/helpers.c')
0 files changed, 0 insertions, 0 deletions