From: Ian Kent <raven@themaw.net>
To: "P. Christeas" <p_christ@hol.gr>
Cc: Andrew Morton <akpm@osdl.org>, hch@lst.de, linux-kernel@vger.kernel.org
Subject: Re: Regression in Autofs, 2.6.15-git
Date: Sun, 15 Jan 2006 01:06:14 +0800 [thread overview]
Message-ID: <1137258375.2847.19.camel@eagle.themaw.net> (raw)
In-Reply-To: <200601141725.28347.p_christ@hol.gr>
On Sat, 2006-01-14 at 17:25 +0200, P. Christeas wrote:
> On Saturday 14 January 2006 5:11 pm, P. Christeas wrote:
> > Doesn't that mean that mnt==0x0004 ? Clearly wrong. I can also see from
> > Christian's patch that mnt wasn't previously used, so it makes perfect
> > sense for that commit to introduce the oops.
> >
> > I guess the problem lies in autofs4_revalidate (fs/autofs4/root.c:420), the
> > nd->mnt value..
> >
> > I will add a silly validator (mnt>0xff) instead of (mnt) and see..
> Confirmed: ((u32)mnt>0xff) discards the invalid 'mnt' value and the oops
> disappears.
> That is, the autofs4 code needs some debugging :( .
Yes. It's me again.
Could you try this patch please.
--- linux-2.6.15/fs/autofs4/root.c.dumb-nameidata 2006-01-15 01:01:26.000000000 +0800
+++ linux-2.6.15/fs/autofs4/root.c 2006-01-15 01:02:12.000000000 +0800
@@ -193,6 +193,8 @@ static int autofs4_dir_open(struct inode
if (!empty)
d_invalidate(dentry);
+ nd.dentry = dentry;
+ nd.mnt = mnt;
nd.flags = LOOKUP_DIRECTORY;
status = (dentry->d_op->d_revalidate)(dentry, &nd);
next prev parent reply other threads:[~2006-01-14 17:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-14 0:17 Regression in Autofs, 2.6.15-git P. Christeas
2006-01-14 11:34 ` Andrew Morton
2006-01-14 11:50 ` P. Christeas
2006-01-14 11:54 ` Andrew Morton
2006-01-14 12:56 ` P. Christeas
2006-01-14 13:17 ` Andrew Morton
2006-01-14 14:01 ` Al Viro
2006-01-14 14:05 ` P. Christeas
2006-01-14 14:28 ` Ian Kent
2006-01-14 15:11 ` P. Christeas
2006-01-14 15:25 ` P. Christeas
2006-01-14 17:06 ` Ian Kent [this message]
2006-01-14 17:54 ` P. Christeas
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=1137258375.2847.19.camel@eagle.themaw.net \
--to=raven@themaw.net \
--cc=akpm@osdl.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=p_christ@hol.gr \
/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