nanddump: fix initialization of bad blocks oob data buffer

When dumping oob data of a bad block, initialize oobbuf with 0xff, instead of
readbuf.  This avoids bogus oob data on output.

Signed-off-by: Baruch Siach <baruch@tkos.co.il>
Acked-by: Mike Frysinger <vapier@gentoo.org>
Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>

diff --git a/nanddump.c b/nanddump.c
index 358993182de354ad05da993b7eed2cd373c4f722..b7341a5f3272c4d52fb148d4aecc0101ffa3a3a8 100644 (file)
--- a/nanddump.c
+++ b/nanddump.c
@@ -452,7 +452,7 @@ int main(int argc, char * const argv[])
                        continue;
 
                if (badblock) {
-                       memset (readbuf, 0xff, meminfo.oobsize);
+                       memset(oobbuf, 0xff, meminfo.oobsize);
                } else {
                        /* Read OOB data and exit on failure */
                        oob.start = ofs;