dm table: stack 'chunk_sectors' limit to account for target-specific splitting
authorMike Snitzer <snitzer@redhat.com>
Mon, 14 Sep 2020 16:02:23 +0000 (12:02 -0400)
committerMike Snitzer <snitzer@redhat.com>
Tue, 29 Sep 2020 20:33:01 +0000 (16:33 -0400)
commit882ec4e609c1a6de1836e765905f62de1502ae1e
treeb9ab981dd874b0729f764d49f3db5537f8c86446
parent1471308fb5ec4335f9ae9fc65f65048dbe7c336e
dm table: stack 'chunk_sectors' limit to account for target-specific splitting

If target set ti->max_io_len it must be used when stacking
DM device's queue_limits to establish a 'chunk_sectors' that is
compatible with the IO stack.

By using lcm_not_zero() care is taken to avoid blindly overriding the
chunk_sectors limit stacked up by blk_stack_limits().

Depends-on: 07d098e6bbad ("block: allow 'chunk_sectors' to be non-power-of-2")
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
drivers/md/dm-table.c