[JFFS2] Print correct node offset when complaining about broken data CRC
Linux-MTD Mailing List
linux-mtd at lists.infradead.org
Thu Jul 5 01:59:01 EDT 2007
Gitweb: http://git.infradead.org/?p=mtd-2.6.git;a=commit;h=b2e25235fe8b4b6cd8cd6a792cbe883d7417eaac
Commit: b2e25235fe8b4b6cd8cd6a792cbe883d7417eaac
Parent: 9c5ef0fbfa0b0be219290b05a39135b957479251
Author: David Woodhouse <dwmw2 at infradead.org>
AuthorDate: Thu Jul 5 01:57:26 2007 -0400
Committer: David Woodhouse <dwmw2 at infradead.org>
CommitDate: Thu Jul 5 01:57:26 2007 -0400
[JFFS2] Print correct node offset when complaining about broken data CRC
Debugging the hardware problems in OLPC trac #1905 would be a whole lot
easier if the correct node offsets were printed for the offending nodes.
Signed-off-by: David Woodhouse <dwmw2 at infradead.org>
---
fs/jffs2/readinode.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/fs/jffs2/readinode.c b/fs/jffs2/readinode.c
index 170da20..b5baa35 100644
--- a/fs/jffs2/readinode.c
+++ b/fs/jffs2/readinode.c
@@ -104,7 +104,7 @@ static int check_node_data(struct jffs2_sb_info *c, struct jffs2_tmp_dnode_info
if (crc != tn->data_crc) {
JFFS2_NOTICE("wrong data CRC in data node at 0x%08x: read %#08x, calculated %#08x.\n",
- ofs, tn->data_crc, crc);
+ ref_offset(ref), tn->data_crc, crc);
return 1;
}
More information about the linux-mtd-cvs
mailing list