From: "Peter Wächtler" <pwaechtler@loewe-komp.de>
To: Steve Lord <lord@sgi.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: NFS related Oops in 2.4.[39]-xfs
Date: Wed, 17 Oct 2001 15:42:29 +0200 [thread overview]
Message-ID: <3BCD8AC5.8FD733BC@loewe-komp.de> (raw)
In-Reply-To: <200110170928.f9H9SsP07618@jen.americas.sgi.com>
Steve Lord wrote:
>
> Where did you get your kernel (the 2.4.9 version that is) this problem
> sounds familiar, but I am pretty sure we fixed this case in XFS somewhere
> between 2.4.3 and 2.4.9.
>
The following diff was made in 2.4.4.
diff -u --recursive --new-file v2.4.4/linux/fs/nfsd/nfsfh.c linux/fs/nfsd/nfsfh.c
--- v2.4.4/linux/fs/nfsd/nfsfh.c Fri Feb 9 11:29:44 2001
+++ linux/fs/nfsd/nfsfh.c Sat May 19 17:47:55 2001
@@ -244,6 +245,11 @@
*/
pdentry = child->d_inode->i_op->lookup(child->d_inode, tdentry);
d_drop(tdentry); /* we never want ".." hashed */
+ if (!pdentry && tdentry->d_inode == NULL) {
+ /* File system cannot find ".." ... sad but possible */
+ dput(tdentry);
+ pdentry = ERR_PTR(-EINVAL);
+ }
But it would not prevent the code path 2.4.3-xfs hit.
pdentry is !=NULL and tdentry->d_inode is always NULL after d_alloc():611
Does xfs' child->d_inode->i_op->lookup(child->d_inode, tdentry);
change the contents of tdentry if the lookup("..") succeeds?
Then I suggest:
! if (!pdentry || tdentry->d_inode == NULL) {
What do you think?
BTW, when does a lookup("..") fail? Even in "/", lookup("..") returns "."
> > struct dentry *nfsd_findparent(struct dentry *child)
> > {
> > struct dentry *tdentry, *pdentry;
> > tdentry = d_alloc(child, &(const struct qstr) {"..", 2, 0});
> > if (!tdentry)
> > return ERR_PTR(-ENOMEM);
> >
> > /* I'm going to assume that if the returned dentry is different, then
> > * it is well connected. But nobody returns different dentrys do they?
> > */
> > pdentry = child->d_inode->i_op->lookup(child->d_inode, tdentry);
> > d_drop(tdentry); /* we never want ".." hashed */
+ if (!pdentry && tdentry->d_inode == NULL) {
+ /* File system cannot find ".." ... sad but possible */
+ dput(tdentry);
+ pdentry = ERR_PTR(-EINVAL);
+ }
> > if (!pdentry) {
> > /* I don't want to return a ".." dentry.
> > * I would prefer to return an unconnected "IS_ROOT" dentry,
> > * though a properly connected dentry is even better
> > */
> > /* if first or last of alias list is not tdentry, use that
> > * else make a root dentry
> > */
> > struct list_head *aliases = &tdentry->d_inode->i_dentry;
> > spin_lock(&dcache_lock);
> > if (aliases->next != aliases) { <=========== CRASH
> > pdentry = list_entry(aliases->next, struct dentry, d_
next prev parent reply other threads:[~2001-10-17 13:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-17 9:14 NFS related Oops in 2.4.[39]-xfs Peter Wächtler
2001-10-17 9:28 ` Steve Lord
2001-10-17 10:00 ` Peter Wächtler
2001-10-17 10:58 ` NET_PROFILE results for 2.4.12 [was sentto is slow] Martin Devera
2001-10-17 13:42 ` Peter Wächtler [this message]
2001-10-17 13:53 ` NFS related Oops in 2.4.[39]-xfs Peter Wächtler
2001-10-17 14:50 ` Steve Lord
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=3BCD8AC5.8FD733BC@loewe-komp.de \
--to=pwaechtler@loewe-komp.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lord@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.