diff options
| author | Niklas Cassel <cassel@kernel.org> | 2026-09-29 10:24:59 +0200 |
|---|---|---|
| committer | Martin K. Petersen (Oracle) <mkp@kernel.org> | 2026-10-03 10:14:29 -0400 |
| commit | e5ebe632be40c60ca8d96c8265c9c8c8136aff4a (patch) | |
| tree | 778a74ad5588f0ec4278b72cae30facacf746bb9 /tools/lib/python/kdoc/python_version.py | |
| parent | 45ce384be0cd83116f8440378beef138b9e92a2b (diff) | |
| download | linux-next-e5ebe632be40c60ca8d96c8265c9c8c8136aff4a.tar.gz linux-next-e5ebe632be40c60ca8d96c8265c9c8c8136aff4a.zip | |
scsi: scsi_debug: Make atomic writes and ZBC emulation mutually exclusive
There are no SMR drives that support atomic writes, so emulating a device
with both emulates something a user cannot encounter, and means maintaining
the zone handling of a command that no zoned device implements.
Nothing in the standards forbids the combination, and for a host managed
drive whose logical block size equals its physical block size there is no
problem in it either: the vendor only has to give atomic writes an
alignment that makes sense with regards to ZBC. This is a choice not to
complicate scsi_debug.
Refuse the combination at initialisation. It can be changed back if such
drives ever appear.
Suggested-by: Damien Le Moal <dlemoal@kernel.org>
Assisted-by: LLM
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-17-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