diff options
| author |   John Garry <john.g.garry@oracle.com> | 2025-01-09 11:40:00 +0000 |
|---|---|---|
| committer |   Jens Axboe <axboe@kernel.dk> | 2025-01-15 09:47:43 -0700 |
| commit | 5d1f7ee7f0b6362c9148d500aeebe49b64b64df4 (patch) | |
| tree | db1cfa5dfa5d0aad602f768af04340557cd4a23e /scripts/generate_rust_analyzer.py | |
| parent | block: Ensure start sector is aligned for stacking atomic writes (diff) | |
| download | wireguard-linux-5d1f7ee7f0b6362c9148d500aeebe49b64b64df4.tar.xz wireguard-linux-5d1f7ee7f0b6362c9148d500aeebe49b64b64df4.zip | |
block: Change blk_stack_atomic_writes_limits() unit_min check
The current check in blk_stack_atomic_writes_limits() for a bottom device
supporting atomic writes is to verify that limit atomic_write_unit_min is
non-zero.
This would cause a problem for device mapper queue limits calculation. This
is because it uses a temporary queue_limits structure to stack the limits,
before finally commiting the limits update.
The value of atomic_write_unit_min for the temporary queue_limits
structure is never evaluated and so cannot be used, so use limit
atomic_write_hw_unit_min.
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: John Garry <john.g.garry@oracle.com>
Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
Link: https://lore.kernel.org/r/20250109114000.2299896-3-john.g.garry@oracle.com
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions