diff options
| author | Christoph Hellwig <hch@lst.de> | 2024-06-13 10:48:20 +0200 |
|---|---|---|
| committer | Jens Axboe <axboe@kernel.dk> | 2024-06-14 18:20:06 +0200 |
| commit | 3c3e85ddffae93eba1a257eb6939bf5dc1e93b9e (patch) | |
| tree | b69e5827ba95b9079e2d89e05b30ddb0fcf6a193 /scripts/extract-ikconfig | |
| parent | block: don't require stable pages for non-PI metadata (diff) | |
| download | linux-3c3e85ddffae93eba1a257eb6939bf5dc1e93b9e.tar.xz linux-3c3e85ddffae93eba1a257eb6939bf5dc1e93b9e.zip | |
block: bypass the STABLE_WRITES flag for protection information
Currently registering a checksum-enabled (aka PI) integrity profile sets
the QUEUE_FLAG_STABLE_WRITE flag, and unregistering it clears the flag.
This can incorrectly clear the flag when the driver requires stable
writes even without PI, e.g. in case of iSCSI or NVMe/TCP with data
digest enabled.
Fix this by looking at the csum_type directly in bdev_stable_writes and
not setting the queue flag. Also remove the blk_queue_stable_writes
helper as the only user in nvme wants to only look at the actual
QUEUE_FLAG_STABLE_WRITE flag as it inherits the integrity configuration
by other means.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
Reviewed-by: Hannes Reinecke <hare@suse.de>
Link: https://lore.kernel.org/r/20240613084839.1044015-11-hch@lst.de
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions