diff options
author | Miquel Raynal <miquel.raynal@free-electrons.com> | 2018-01-12 12:13:36 +0300 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2018-02-16 22:14:44 +0300 |
commit | 0dcc0912d39465102ffc5cd44ce6ac8d2d5c8933 (patch) | |
tree | f89ee928a1f35597e798d2629e5ac6ae43393c50 /fs/nfs | |
parent | 6cd23a0e51dd2580bfdbb005ad1edeeaf9192d00 (diff) | |
download | linux-0dcc0912d39465102ffc5cd44ce6ac8d2d5c8933.tar.xz |
mtd: nand: Fix nand_do_read_oob() return value
commit 87e89ce8d0d14f573c068c61bec2117751fb5103 upstream.
Starting from commit 041e4575f034 ("mtd: nand: handle ECC errors in
OOB"), nand_do_read_oob() (from the NAND core) did return 0 or a
negative error, and the MTD layer expected it.
However, the trend for the NAND layer is now to return an error or a
positive number of bitflips. Deciding which status to return to the user
belongs to the MTD layer.
Commit e47f68587b82 ("mtd: check for max_bitflips in mtd_read_oob()")
brought this logic to the mtd_read_oob() function while the return value
coming from nand_do_read_oob() (called by the ->_read_oob() hook) was
left unchanged.
Fixes: e47f68587b82 ("mtd: check for max_bitflips in mtd_read_oob()")
Signed-off-by: Miquel Raynal <miquel.raynal@free-electrons.com>
Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs/nfs')
0 files changed, 0 insertions, 0 deletions