diff options
| author | Benjamin Marzinski <bmarzins@redhat.com> | 2025-04-10 15:49:40 -0400 |
|---|---|---|
| committer | Mikulas Patocka <mpatocka@redhat.com> | 2025-04-11 13:38:53 +0200 |
| commit | 4ea30ec6fb3bb598bd1df04cdfab13b1140074d2 (patch) | |
| tree | 788c040a4d7246bca260456df7a37256b2b4be3f /net/lapb/lapb_timer.c | |
| parent | e8819e7f03470c5b468720630d9e4e1d5b99159e (diff) | |
dm: handle failures in dm_table_set_restrictions
If dm_table_set_restrictions() fails while swapping tables,
device-mapper will continue using the previous table. It must be sure to
leave the mapped_device in it's previous state on failure. Otherwise
device-mapper could end up using the old table with settings from the
unused table.
Do not update the mapped device in dm_set_zones_restrictions(). Wait
till after dm_table_set_restrictions() is sure to succeed to update the
md zoned settings. Do the same with the dax settings, and if
dm_revalidate_zones() fails, restore the original queue limits.
Fixes: 7f91ccd8a608d ("dm: Call dm_revalidate_zones() after setting the queue limits")
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 'net/lapb/lapb_timer.c')
0 files changed, 0 insertions, 0 deletions