summaryrefslogtreecommitdiff
path: root/tools/lib/python/kdoc
diff options
context:
space:
mode:
authorNiklas Cassel <cassel@kernel.org>2026-09-29 10:25:10 +0200
committerMartin K. Petersen (Oracle) <mkp@kernel.org>2026-10-03 10:14:30 -0400
commita6c339feb830daa097ccc4c50c339c1733c12d42 (patch)
tree846acf472e98c353b81bb9f9d85fa253a063c212 /tools/lib/python/kdoc
parent491bd55c35cbb1ce059f22e7f3c6284551970fef (diff)
downloadlinux-next-a6c339feb830daa097ccc4c50c339c1733c12d42.tar.gz
linux-next-a6c339feb830daa097ccc4c50c339c1733c12d42.zip
scsi: scsi_debug: Validate the access parameters of WRITE ATOMIC (16)
resp_atomic_write() validates the fields that are specific to an atomic write, but never the range that the command addresses. Every other command that writes user data calls check_device_access_params() first, which rejects a transfer that ends beyond the capacity of the device, one whose length exceeds the size of the store, and any write to a write protected device. Call check_device_access_params(). The zone checks that it ends with are unreachable, as atomic writes and ZBC emulation are mutually exclusive. Assisted-by: LLM Fixes: 84f3a3c01d70 ("scsi: scsi_debug: Atomic write support") Reviewed-by: Damien Le Moal <dlemoal@kernel.org> Reviewed-by: John Garry <john.garry@linux.dev> Signed-off-by: Niklas Cassel <cassel@kernel.org> Link: https://patch.msgid.link/20260929082456.857423-28-cassel@kernel.org Signed-off-by: Martin K. Petersen (Oracle) <mkp@kernel.org>
Diffstat (limited to 'tools/lib/python/kdoc')
0 files changed, 0 insertions, 0 deletions