diff options
| author | Niklas Cassel <cassel@kernel.org> | 2026-09-29 10:25:07 +0200 |
|---|---|---|
| committer | Martin K. Petersen (Oracle) <mkp@kernel.org> | 2026-10-03 10:14:30 -0400 |
| commit | cb2d2a7c80c62d1e5e476609706f29dd9584d0e0 (patch) | |
| tree | 1fa6ce276e34d7057b1a540b5b90d8c2a22473e1 /tools/lib/python/kdoc/python_version.py | |
| parent | b8fad9f02485f179e35bc4677386b6608d8cefb0 (diff) | |
| download | linux-next-cb2d2a7c80c62d1e5e476609706f29dd9584d0e0.tar.gz linux-next-cb2d2a7c80c62d1e5e476609706f29dd9584d0e0.zip | |
scsi: scsi_debug: Advance the write pointer over the data written
resp_write_dt0() and resp_write_scat() advance the write pointer of a
sequential write required zone by the transfer length of the command
without looking at what do_device_access() returned, which is -1 when the
data direction of the command does not match the operation, and a short
byte count when the data-out buffer is smaller than the transfer length. An
initiator can produce both with SG_IO.
The zone then describes more data than is on the medium, and a write at the
position where the data really ends is terminated with UNALIGNED WRITE
COMMAND, so the zone has to be reset before it can be written to again.
Advance the write pointer over the data that was written instead. As
do_device_access() does not write a partial physical block to such a zone,
that leaves the write pointer where a write can end.
Assisted-by: LLM
Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
Fixes: f0d1cf9378bd ("scsi: scsi_debug: Add ZBC zone commands")
Signed-off-by: Niklas Cassel <cassel@kernel.org>
Link: https://patch.msgid.link/20260929082456.857423-25-cassel@kernel.org
Signed-off-by: Martin K. Petersen (Oracle) <mkp@kernel.org>
Diffstat (limited to 'tools/lib/python/kdoc/python_version.py')
0 files changed, 0 insertions, 0 deletions
