summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDavid Woodhouse <dwmw2@infradead.org>2007-07-05 01:57:26 -0400
committerDavid Woodhouse <dwmw2@infradead.org>2007-07-05 01:57:26 -0400
commitb2e25235fe8b4b6cd8cd6a792cbe883d7417eaac (patch)
tree7f55270f3f208d59aa973c6660acf92d0aa62ae0
parent9c5ef0fbfa0b0be219290b05a39135b957479251 (diff)
downloadblackbird-op-linux-b2e25235fe8b4b6cd8cd6a792cbe883d7417eaac.tar.gz
blackbird-op-linux-b2e25235fe8b4b6cd8cd6a792cbe883d7417eaac.zip
[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@infradead.org>
-rw-r--r--fs/jffs2/readinode.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/jffs2/readinode.c b/fs/jffs2/readinode.c
index 170da20b97c7..b5baa356fed2 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;
}
OpenPOWER on IntegriCloud