diff options
author | Frieder Schrempf <frieder.schrempf@kontron.de> | 2020-02-18 10:05:14 +0000 |
---|---|---|
committer | Miquel Raynal <miquel.raynal@bootlin.com> | 2020-03-11 16:17:54 +0100 |
commit | 2148937501ee3d663e0010e519a553fea67ad103 (patch) | |
tree | 71813442260de64629af61328afd1863066e958d /drivers/rtc/rtc-rs5c348.c | |
parent | 7f274f411c76ecf87c6eef7ce263ddfe0962ba46 (diff) | |
download | linux-2148937501ee3d663e0010e519a553fea67ad103.tar.bz2 |
mtd: spinand: Stop using spinand->oobbuf for buffering bad block markers
For reading and writing the bad block markers, spinand->oobbuf is
currently used as a buffer for the marker bytes. During the
underlying read and write operations to actually get/set the content
of the OOB area, the content of spinand->oobbuf is reused and changed
by accessing it through spinand->oobbuf and/or spinand->databuf.
This is a flaw in the original design of the SPI NAND core and at the
latest from 13c15e07eedf ("mtd: spinand: Handle the case where
PROGRAM LOAD does not reset the cache") on, it results in not having
the bad block marker written at all, as the spinand->oobbuf is
cleared to 0xff after setting the marker bytes to zero.
To fix it, we now just store the two bytes for the marker on the
stack and let the read/write operations copy it from/to the page
buffer later.
Fixes: 7529df465248 ("mtd: nand: Add core infrastructure to support SPI NANDs")
Cc: stable@vger.kernel.org
Signed-off-by: Frieder Schrempf <frieder.schrempf@kontron.de>
Reviewed-by: Boris Brezillon <boris.brezillon@collabora.com>
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
Link: https://lore.kernel.org/linux-mtd/20200218100432.32433-2-frieder.schrempf@kontron.de
Diffstat (limited to 'drivers/rtc/rtc-rs5c348.c')
0 files changed, 0 insertions, 0 deletions