[lkml]   [2012]   [Apr]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Patch in this message
    Subject[ 05/42] mtd: block2mtd: initialize writebufsize
    3.0-stable review patch.  If anyone has any objections, please let me know.


    From: Artem Bityutskiy <>

    commit b604387411ec6a072e95910099262616edd2bd2f upstream.

    The writebufsize concept was introduce by commit
    "0e4ca7e mtd: add writebufsize field to mtd_info struct" and it represents
    the maximum amount of data the device writes to the media at a time. This is
    an important parameter for UBIFS which is used during recovery and which
    basically defines how big a corruption caused by a power cut can be.

    However, we forgot to set this parameter for block2mtd. Set it to PAGE_SIZE
    because this is actually the amount of data we write at a time.

    Signed-off-by: Artem Bityutskiy <>
    Acked-by: Joern Engel <>
    Signed-off-by: David Woodhouse <>
    Signed-off-by: Greg Kroah-Hartman <>

    drivers/mtd/devices/block2mtd.c | 1 +
    1 file changed, 1 insertion(+)

    --- a/drivers/mtd/devices/block2mtd.c
    +++ b/drivers/mtd/devices/block2mtd.c
    @@ -284,6 +284,7 @@ static struct block2mtd_dev *add_device(
    dev->mtd.size = dev->blkdev->bd_inode->i_size & PAGE_MASK;
    dev->mtd.erasesize = erase_size;
    dev->mtd.writesize = 1;
    + dev->mtd.writebufsize = PAGE_SIZE;
    dev->mtd.type = MTD_RAM;
    dev->mtd.flags = MTD_CAP_RAM;
    dev->mtd.erase = block2mtd_erase;

     \ /
      Last update: 2012-04-12 01:41    [W:0.029 / U:7.432 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site