From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: "J. R. Okajima" <hooanon05@yahoo.co.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: O_EXCL in NFSv3
Date: Tue, 12 Apr 2011 07:56:11 -0400 [thread overview]
Message-ID: <1302609371.10760.6.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20361.1302593733@jrobl>
On Tue, 2011-04-12 at 16:35 +0900, J. R. Okajima wrote:
> Hello Trond,
>
> The commit in v2.6.37
> c0204fd 2010-09-17 NFS: Clean up nfs4_proc_create()
> looks totally dropping O_EXCL flag from NFSv3.
> But fs/nfs/nfs3proc.c:nfs3_proc_create() and
> fs/nfsd/nfs3proc.c:nfsd3_proc_create() still expect O_EXCL to be passed.
>
> And the commit log says "Clean up nfs4_proc_create()".
> Is this change for NFSv3 intentional?
> Actually O_EXCL in NFSv3 doesn't work in v2.6.37 and later.
Doesn't commit 8a0eebf66e3b1deae036553ba641a9c2bdbae678 (NFS: Fix NFSv3
exclusive open semantics) fix this? It should be in the stable tree.
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
next prev parent reply other threads:[~2011-04-12 11:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 7:35 J. R. Okajima
2011-04-12 11:56 ` Trond Myklebust [this message]
2011-04-12 12:15 ` J. R. Okajima
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=1302609371.10760.6.camel@lade.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=hooanon05@yahoo.co.jp \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®