lkml.org 
[lkml]   [2013]   [Nov]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH 3.4 32/39] block: properly stack underlying max_segment_size to DM device
    Date
    3.4-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>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

    ---
    block/blk-settings.c | 1 +
    1 file changed, 1 insertion(+)

    --- a/block/blk-settings.c
    +++ b/block/blk-settings.c
    @@ -143,6 +143,7 @@ void blk_set_stacking_limits(struct queu
    lim->discard_zeroes_data = 1;
    lim->max_segments = USHRT_MAX;
    lim->max_hw_sectors = UINT_MAX;
    + lim->max_segment_size = UINT_MAX;

    lim->max_sectors = BLK_DEF_MAX_SECTORS;
    }



    \
     
     \ /
      Last update: 2013-11-27 07:41    [W:4.212 / U:0.136 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site