diff options
| author | Anuj Gupta <anuj20.g@samsung.com> | 2025-03-05 09:30:33 +0300 |
|---|---|---|
| committer | Jens Axboe <axboe@kernel.dk> | 2025-03-06 18:01:37 +0300 |
| commit | 85f72925000e924291a0ebf63d2234994a4f22bd (patch) | |
| tree | 1fef4ab6ff4bce6d9b6776fc5f18749f1b282ade /tools/perf/scripts/python/failed-syscalls-by-pid.py | |
| parent | 677e332e4885a17def5efa4788b6e725a737b63c (diff) | |
| download | linux-85f72925000e924291a0ebf63d2234994a4f22bd.tar.xz | |
block: Correctly initialize BLK_INTEGRITY_NOGENERATE and BLK_INTEGRITY_NOVERIFY
Currently, BLK_INTEGRITY_NOGENERATE and BLK_INTEGRITY_NOVERIFY are not
explicitly set during integrity initialization. This can lead to
incorrect reporting of read_verify and write_generate sysfs values,
particularly when a device does not support integrity. Ensure that these
flags are correctly initialized by default.
Reported-by: M Nikhil <nikh1092@linux.ibm.com>
Link: https://lore.kernel.org/linux-block/f6130475-3ccd-45d2-abde-3ccceada0f0a@linux.ibm.com/
Fixes: 9f4aa46f2a74 ("block: invert the BLK_INTEGRITY_{GENERATE,VERIFY} flags")
Signed-off-by: Anuj Gupta <anuj20.g@samsung.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Link: https://lore.kernel.org/r/20250305063033.1813-3-anuj20.g@samsung.com
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'tools/perf/scripts/python/failed-syscalls-by-pid.py')
0 files changed, 0 insertions, 0 deletions