diff options
| author | Niklas Cassel <cassel@kernel.org> | 2026-09-29 10:25:09 +0200 |
|---|---|---|
| committer | Martin K. Petersen (Oracle) <mkp@kernel.org> | 2026-10-03 10:14:30 -0400 |
| commit | 491bd55c35cbb1ce059f22e7f3c6284551970fef (patch) | |
| tree | fe731ba76444bc3957c46ec03532b66cb3858f52 /tools/lib/python/kdoc/python_version.py | |
| parent | b81608b17c5d04c797e6fc1cfb95182c842a4db9 (diff) | |
| download | linux-next-491bd55c35cbb1ce059f22e7f3c6284551970fef.tar.gz linux-next-491bd55c35cbb1ce059f22e7f3c6284551970fef.zip | |
scsi: scsi_debug: Map the region written by WRITE ATOMIC (16)
When logical block provisioning is enabled, every command that writes user
data calls map_region() so that GET LBA STATUS reports the region as
mapped. resp_atomic_write() does not, so GET LBA STATUS keeps reporting a
region as deallocated after a WRITE ATOMIC (16) has written it.
Call map_region() the way resp_write_dt0() does, holding the zone metadata
write lock across the access. That lock is what serialises the map against
resp_unmap(), which does nothing unless logical block provisioning is
enabled.
Assisted-by: LLM
Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
Reviewed-by: John Garry <john.garry@linux.dev>
Fixes: 84f3a3c01d70 ("scsi: scsi_debug: Atomic write support")
Signed-off-by: Niklas Cassel <cassel@kernel.org>
Link: https://patch.msgid.link/20260929082456.857423-27-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