| From | Luis Henriques <> | Subject | [PATCH 3.5 22/90] block: properly stack underlying max_segment_size to DM device | Date | Thu, 5 Dec 2013 17:35:04 +0000 |
| |
3.5.7.27 -stable review patch. If anyone has any objections, please let me know.
------------------
From: Mike Snitzer <snitzer@redhat.com>
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> [ luis: backported to 3.5: adjusted context ] Signed-off-by: Luis Henriques <luis.henriques@canonical.com> --- block/blk-settings.c | 1 + 1 file changed, 1 insertion(+)
diff --git a/block/blk-settings.c b/block/blk-settings.c index d3234fc..191d33e 100644 --- a/block/blk-settings.c +++ b/block/blk-settings.c @@ -144,6 +144,7 @@ void blk_set_stacking_limits(struct queue_limits *lim) lim->max_segments = USHRT_MAX; lim->max_hw_sectors = UINT_MAX; + lim->max_segment_size = UINT_MAX; lim->max_sectors = BLK_DEF_MAX_SECTORS; } EXPORT_SYMBOL(blk_set_stacking_limits); -- 1.8.3.2
|