summaryrefslogtreecommitdiff
path: root/fs/jffs2/nodemgmt.c
diff options
context:
space:
mode:
authorDavid Woodhouse <dwmw2@infradead.org>2007-06-28 19:03:11 +0100
committerDavid Woodhouse <dwmw2@infradead.org>2007-06-28 19:03:11 +0100
commit66bfaeaa90432a585d7e9e70605ee4df3ede9890 (patch)
tree31c585ef0afff2420a9a13930842c1d82bb084f3 /fs/jffs2/nodemgmt.c
parentd364fb18cd991734eb54aa8840e70030b0c9f699 (diff)
downloadlwn-66bfaeaa90432a585d7e9e70605ee4df3ede9890.tar.gz
lwn-66bfaeaa90432a585d7e9e70605ee4df3ede9890.zip
[JFFS2] Improve diagnostic output for 'node added in wrong place' check
Jocke has seen this fail. We want to know why. Signed-off-by: David Woodhouse <dwmw2@infradead.org>
Diffstat (limited to 'fs/jffs2/nodemgmt.c')
-rw-r--r--fs/jffs2/nodemgmt.c7
1 files changed, 6 insertions, 1 deletions
diff --git a/fs/jffs2/nodemgmt.c b/fs/jffs2/nodemgmt.c
index dbc908ad622b..9c3a3bba6dcf 100644
--- a/fs/jffs2/nodemgmt.c
+++ b/fs/jffs2/nodemgmt.c
@@ -423,7 +423,12 @@ struct jffs2_raw_node_ref *jffs2_add_physical_node_ref(struct jffs2_sb_info *c,
even after refiling c->nextblock */
if ((c->nextblock || ((ofs & 3) != REF_OBSOLETE))
&& (jeb != c->nextblock || (ofs & ~3) != jeb->offset + (c->sector_size - jeb->free_size))) {
- printk(KERN_WARNING "argh. node added in wrong place\n");
+ printk(KERN_WARNING "argh. node added in wrong place at 0x%08x(%d)\n", ofs & ~3, ofs & 3);
+ if (c->nextblock)
+ printk(KERN_WARNING "nextblock 0x%08x", c->nextblock->offset);
+ else
+ printk(KERN_WARNING "No nextblock");
+ printk(", expected at %08x\n", jeb->offset + (c->sector_size - jeb->free_size));
return ERR_PTR(-EINVAL);
}
#endif