mtd: Make sure mtd->erasesize is valid even if the partition is of size 0
authorBoris Brezillon <bbrezillon@kernel.org>
Wed, 30 Jan 2019 11:55:52 +0000 (12:55 +0100)
committerBoris Brezillon <bbrezillon@kernel.org>
Tue, 5 Feb 2019 23:02:51 +0000 (00:02 +0100)
commitad4635153034c20c6f6e211e2ed3fd38b658649a
tree528a506354beb97de16e105d81babf3d3ad813d2
parentbda2ab56356b9acdfab150f31c4bac9846253092
mtd: Make sure mtd->erasesize is valid even if the partition is of size 0

Commit 33f45c44d68b ("mtd: Do not allow MTD devices with inconsistent
erase properties") introduced a check to make sure ->erasesize and
->_erase values are consistent with the MTD_NO_ERASE flag.
This patch did not take the 0 bytes partition case into account which
can happen when the defined partition is outside the flash device memory
range. Fix that by setting the partition erasesize to the parent
erasesize.

Fixes: 33f45c44d68b ("mtd: Do not allow MTD devices with inconsistent erase properties")
Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: <stable@vger.kernel.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>
Signed-off-by: Boris Brezillon <bbrezillon@kernel.org>
Tested-by: Geert Uytterhoeven <geert+renesas@glider.be>
drivers/mtd/mtdpart.c