block: properly stack underlying max_segment_size to DM device
authorMike Snitzer <snitzer@redhat.com>
Fri, 18 Oct 2013 15:44:49 +0000 (09:44 -0600)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Fri, 29 Nov 2013 18:50:36 +0000 (10:50 -0800)
commit801327994060b0ae3749257d264a7bfea119b46c
treef06d24743c51b4aa314d44c452ccc6642298ce74
parent82b80fae0eb0c2d18414f7e678e04a4e7f88ecbe
block: properly stack underlying max_segment_size to DM device

commit d82ae52e68892338068e7559a0c0657193341ce4 upstream.

Without this patch all DM devices will default to BLK_MAX_SEGMENT_SIZE
(65536) even if the underlying device(s) have a larger value -- this is
due to blk_stack_limits() using min_not_zero() when stacking the
max_segment_size limit.

1073741824

before patch:
65536

after patch:
1073741824

Reported-by: Lukasz Flis <l.flis@cyfronet.pl>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
block/blk-settings.c