diff options
author | 2025-04-10 15:49:43 -0400 | |
---|---|---|
committer | 2025-05-04 11:35:05 +0200 | |
commit | ad320ae27661f91585e00c114d1b264130f1bebe (patch) | |
tree | 60c8263079aaefed61a66550662a675281c28a20 /scripts/lib/kdoc/kdoc_files.py | |
parent | dm: limit swapping tables for devices with zone write plugs (diff) | |
download | linux-rng-ad320ae27661f91585e00c114d1b264130f1bebe.tar.xz linux-rng-ad320ae27661f91585e00c114d1b264130f1bebe.zip |
dm: fix native zone append devices on top of emulated ones
If a DM device that can pass down zone append commands is stacked on top
of a device that emulates zone append commands, it will allocate zone
append emulation resources, even though it doesn't use them. This is
because the underlying device will have max_hw_zone_append_sectors set
to 0 to request zone append emulation. When the DM device is stacked on
top of it, it will inherit that max_hw_zone_append_sectors limit,
despite being able to pass down zone append bios. Solve this by making
sure max_hw_zone_append_sectors is non-zero for DM devices that do not
need zone append emulation.
Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
Tested-by: Damien Le Moal <dlemoal@kernel.org>
Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com>
Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_files.py')
0 files changed, 0 insertions, 0 deletions