diff options
author | Christoph Hellwig <hch@lst.de> | 2024-07-02 17:10:23 +0200 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2024-07-03 10:21:16 -0600 |
commit | 85253bac4d02b1f95d6109c221aeccd7a262ec4d (patch) | |
tree | 14ebb70a5ead12a05e1b4d1270241c399ca00994 /include/linux/math64.h | |
parent | f8924374fd37a8b41d554acd8b7407af7d354c0d (diff) |
block: don't free submitter owned integrity payload on I/O completion
Currently __bio_integrity_endio frees the integrity payload unless it is
explicitly marked as user-mapped. This means in-kernel callers that
allocate their own integrity payload never get to see it on I/O
completion. The current two users don't need it as they just pre-mapped
PI tuples received over the network, but this limits uses of integrity
data lot.
Change bio_integrity_endio to call __bio_integrity_endio for block layer
generated integrity data only, and leave freeing of submitter
allocated integrity data to bio_uninit which also gets called from
the final bio_put. This requires that unmapping user mapped or copied
integrity data is now always done by the caller, and the special
BIP_INTEGRITY_USER flag can go away.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Reviewed-by: Kanchan Joshi <joshi.k@samsung.com>
Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
Link: https://lore.kernel.org/r/20240702151047.1746127-6-hch@lst.de
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'include/linux/math64.h')
0 files changed, 0 insertions, 0 deletions