diff options
author | pekon gupta <pekon@ti.com> | 2014-03-20 18:49:58 +0530 |
---|---|---|
committer | Brian Norris <computersforpeace@gmail.com> | 2014-05-20 16:32:17 -0700 |
commit | f306e8c3b667632952f1a4a74ffb910bbc06255f (patch) | |
tree | fcefd08db04a0106077e81d503a02f778dc07857 /drivers/mtd/mtdchar.c | |
parent | 9ab86995ed07f51c45ba1b549aff2bd6e46590e9 (diff) | |
download | linux-stable-f306e8c3b667632952f1a4a74ffb910bbc06255f.tar.gz linux-stable-f306e8c3b667632952f1a4a74ffb910bbc06255f.tar.bz2 linux-stable-f306e8c3b667632952f1a4a74ffb910bbc06255f.zip |
mtd: nand: omap: fix BCHx ecc.correct to return detected bit-flips in erased-page
fixes: commit 62116e5171e00f85a8d53f76e45b84423c89ff34
mtd: nand: omap2: Support for hardware BCH error correction.
In omap_elm_correct_data(), if bitflip_count in an erased-page is within the
correctable limit (< ecc.strength), then it is not indicated back to the caller
ecc->read_page().
This mis-guides upper layers like MTD and UBIFS layer to assume erased-page as
perfectly clean and use it for writing even if actual bitflip_count was
dangerously high (bitflip_count > mtd->bitflip_threshold).
This patch fixes this above issue, by returning 'stats' to caller
ecc->read_page() under all scenarios.
Reported-by: Brian Norris <computersforpeace@gmail.com>
Signed-off-by: Pekon Gupta <pekon@ti.com>
Cc: <stable@vger.kernel.org> # 3.9.x+
Signed-off-by: Brian Norris <computersforpeace@gmail.com>
Diffstat (limited to 'drivers/mtd/mtdchar.c')
0 files changed, 0 insertions, 0 deletions