From: Adam Lackorzynski <adam@os.inf.tu-dresden.de>
To: Bian Naimeng <biannm@cn.fujitsu.com>
Cc: Trond Myklebust <Trond.Myklebust@netapp.com>,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
stable@kernel.org
Subject: Re: 2.6.35.2: NFS related Oops
Date: Wed, 18 Aug 2010 13:36:10 +0200 [thread overview]
Message-ID: <20100818113610.GA27174@os.inf.tu-dresden.de> (raw)
In-Reply-To: <4C6B4A20.60507@cn.fujitsu.com>
On Wed Aug 18, 2010 at 10:49:04 +0800, Bian Naimeng wrote:
> >>> /* We can't create new files, or truncate existing ones here */
> >>> openflags &= ~(O_CREAT|O_TRUNC);
> >>> --
> >> Nope. The problem is the recent switch to LOOKUP_EXCL as the authority
> >> for whether or not we're doing an exclusive create.
> >>
> >> Does the following patch work?
> >>
> >
> > Hi Trond, i guess it's not work.
> >
> > As i see, if we want get LOOKUP_EXCL at nd->flags, we must open file with
> > O_CREAT and O_EXCL, "nd->flags & LOOKUP_EXCL" have the same effect with
> > "(openflags & (O_CREAT|O_EXCL)) == (O_CREAT|O_EXCL)", so i think the kernel
> > still crash, right?
I can confirm, it's oopsing.
> What about this one?
This one works.
>
> We we open a positive file just with O_EXCL but no O_CREAT, may cause kernel crash.
>
> Signed-off-by: Bian Naimeng <biannm@cn.fujitsu.com>
>
> ---
> fs/namei.c | 7 +++----
> fs/nfs/dir.c | 2 +-
> 2 files changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/fs/namei.c b/fs/namei.c
> index 17ea76b..6680a38 100644
> --- a/fs/namei.c
> +++ b/fs/namei.c
> @@ -1813,11 +1813,10 @@ reval:
> nd.intent.open.create_mode = mode;
> nd.flags &= ~LOOKUP_PARENT;
> nd.flags |= LOOKUP_OPEN;
> - if (open_flag & O_CREAT) {
> + if (open_flag & O_CREAT)
> nd.flags |= LOOKUP_CREATE;
> - if (open_flag & O_EXCL)
> - nd.flags |= LOOKUP_EXCL;
> - }
> + if (open_flag & O_EXCL)
> + nd.flags |= LOOKUP_EXCL;
> if (open_flag & O_DIRECTORY)
> nd.flags |= LOOKUP_DIRECTORY;
> if (!(open_flag & O_NOFOLLOW))
> diff --git a/fs/nfs/dir.c b/fs/nfs/dir.c
> index 29539ce..bc25da9 100644
> --- a/fs/nfs/dir.c
> +++ b/fs/nfs/dir.c
> @@ -1100,7 +1100,7 @@ static int nfs_open_revalidate(struct dentry *dentry, struct nameidata *nd)
> goto no_open_dput;
> openflags = nd->intent.open.flags;
> /* We cannot do exclusive creation on a positive dentry */
> - if ((openflags & (O_CREAT|O_EXCL)) == (O_CREAT|O_EXCL))
> + if (nd->flags & LOOKUP_EXCL)
> goto no_open_dput;
> /* We can't create new files, or truncate existing ones here */
> openflags &= ~(O_CREAT|O_TRUNC);
> --
> 1.7.0
Adam
--
Adam adam@os.inf.tu-dresden.de
Lackorzynski http://os.inf.tu-dresden.de/~adam/
next prev parent reply other threads:[~2010-08-18 11:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 21:50 2.6.35.2: NFS related Oops Adam Lackorzynski
2010-08-17 10:09 ` Bian Naimeng
2010-08-17 17:14 ` Adam Lackorzynski
2010-08-17 22:43 ` Trond Myklebust
2010-08-18 2:12 ` Bian Naimeng
2010-08-18 2:49 ` Bian Naimeng
2010-08-18 11:36 ` Adam Lackorzynski [this message]
2010-08-18 13:36 ` Trond Myklebust
2010-08-18 15:44 ` Adam Lackorzynski
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=20100818113610.GA27174@os.inf.tu-dresden.de \
--to=adam@os.inf.tu-dresden.de \
--cc=Trond.Myklebust@netapp.com \
--cc=biannm@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=stable@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).