lkml.org 
[lkml]   [2020]   [Jun]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH 5.4 219/261] dm crypt: avoid truncating the logical block size
    Date
    From: Eric Biggers <ebiggers@google.com>

    commit 64611a15ca9da91ff532982429c44686f4593b5f upstream.

    queue_limits::logical_block_size got changed from unsigned short to
    unsigned int, but it was forgotten to update crypt_io_hints() to use the
    new type. Fix it.

    Fixes: ad6bf88a6c19 ("block: fix an integer overflow in logical block size")
    Cc: stable@vger.kernel.org
    Signed-off-by: Eric Biggers <ebiggers@google.com>
    Reviewed-by: Mikulas Patocka <mpatocka@redhat.com>
    Signed-off-by: Mike Snitzer <snitzer@redhat.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

    ---
    drivers/md/dm-crypt.c | 2 +-
    1 file changed, 1 insertion(+), 1 deletion(-)

    --- a/drivers/md/dm-crypt.c
    +++ b/drivers/md/dm-crypt.c
    @@ -2957,7 +2957,7 @@ static void crypt_io_hints(struct dm_tar
    limits->max_segment_size = PAGE_SIZE;

    limits->logical_block_size =
    - max_t(unsigned short, limits->logical_block_size, cc->sector_size);
    + max_t(unsigned, limits->logical_block_size, cc->sector_size);
    limits->physical_block_size =
    max_t(unsigned, limits->physical_block_size, cc->sector_size);
    limits->io_min = max_t(unsigned, limits->io_min, cc->sector_size);

    \
     
     \ /
      Last update: 2020-06-19 17:22    [W:6.114 / U:0.044 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site