From: Christoph Hellwig <hch@infradead.org>
To: Martin Spott <Martin.Spott@mgras.net>
Cc: linux-xfs@oss.sgi.com
Subject: Re: Kernel crash with 2.6.29 + nfs + xfs (radix-tree)
Date: Sun, 7 Jun 2009 14:55:58 -0400 [thread overview]
Message-ID: <20090607185558.GA753@infradead.org> (raw)
In-Reply-To: <h0gtcd$136u$1@osprey.mgras.de>
On Sun, Jun 07, 2009 at 05:28:45PM +0000, Martin Spott wrote:
> reconnect_path: npd != pd
> reconnect_path: npd != pd
> reconnect_path: npd != pd
> [...]
>
>
> .... I'm unable to find any helpful information in this context.
> Anything I could try - this sunday evening ?
That warning is what really makes me freak out, as it really, really
shouldn't happen. Can you see if it gives any additional useful output
with the patch below?
Index: linux-2.6/fs/exportfs/expfs.c
===================================================================
--- linux-2.6.orig/fs/exportfs/expfs.c 2009-06-07 20:40:09.085814403 +0200
+++ linux-2.6/fs/exportfs/expfs.c 2009-06-07 20:54:47.550942377 +0200
@@ -88,6 +88,14 @@ find_disconnected_root(struct dentry *de
return dentry;
}
+static void dump_dentry(struct dentry *dentry, const char *var)
+{
+ printk("%s: dentry 0x%p inode 0x%p ino %lld name %s\n",
+ var, dentry, dentry->d_inode,
+ dentry->d_inode ?
+ (unsigned long long)dentry->d_inode->i_ino : 0,
+ dentry->d_name.name);
+}
/*
* Make sure target_dir is fully connected to the dentry tree.
@@ -187,8 +195,11 @@ reconnect_path(struct vfsmount *mnt, str
*/
if (npd == pd)
noprogress = 0;
- else
+ else {
printk("%s: npd != pd\n", __func__);
+ dump_dentry(npd, "npd");
+ dump_dentry(pd, "pd");
+ }
dput(npd);
dput(ppd);
if (IS_ROOT(pd)) {
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-06-07 18:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090520003745.GA27491@samad.com.au>
2009-05-20 9:05 ` Kernel crash with 2.6.29 + nfs + xfs (radix-tree) Dave Chinner
2009-05-20 9:56 ` Alex Samad
2009-05-26 9:09 ` Christoph Hellwig
2009-05-27 2:54 ` Alex Samad
2009-06-04 11:26 ` Christoph Hellwig
2009-06-05 11:20 ` Martin Spott
2009-06-07 17:28 ` Martin Spott
2009-06-07 18:27 ` Felix Blyakher
2009-06-07 18:27 ` Eric Sandeen
2009-06-07 18:55 ` Martin Spott
2009-06-07 18:55 ` Christoph Hellwig [this message]
2009-06-07 20:00 ` Martin Spott
2009-06-07 20:44 ` Christoph Hellwig
2009-06-07 21:26 ` Martin Spott
2009-06-08 20:13 ` Martin Spott
2009-06-09 8:40 ` Christoph Hellwig
2009-05-27 17:21 ` Martin Spott
2009-05-27 18:05 ` Martin Spott
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090607185558.GA753@infradead.org \
--to=hch@infradead.org \
--cc=Martin.Spott@mgras.net \
--cc=linux-xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox