From: Dr James Bruce Fields <bfields@fieldses.org>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: Orion Poplawski <orion@cora.nwra.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [nfsv4] open(O_CREAT) returns EEXISTS on symbolic link created on another system until stat()ed
Date: Thu, 29 Mar 2012 17:17:13 -0400 [thread overview]
Message-ID: <20120329211713.GD21493@fieldses.org> (raw)
In-Reply-To: <20120329210838.GC21493@fieldses.org>
On Thu, Mar 29, 2012 at 05:08:38PM -0400, Dr James Bruce Fields wrote:
> Anyway, something like the following (untested) should change v3 to
> return nfs_ok in this case, and v4 to return the same errors it would on
> a non-create open.
Looking at the history, I think the v3 behavior has been there from the
start. I wonder why we've never gotten a bug report?
Looking at wireshark.... I guess the client always does a lookup first,
so we never hit this case (unless someone replaces the file by a
non-regular-file between a lookup and a create?)
--b.
next prev parent reply other threads:[~2012-03-29 21:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 16:28 [nfsv4] open(O_CREAT) returns EEXISTS on symbolic link created on another system until stat()ed Orion Poplawski
2012-03-29 16:54 ` Myklebust, Trond
[not found] ` <4F749CCA.3000400@cora.nwra.com>
2012-03-29 17:40 ` Myklebust, Trond
2012-03-29 18:07 ` Orion Poplawski
2012-03-29 19:31 ` Dr James Bruce Fields
2012-03-29 20:16 ` Myklebust, Trond
2012-03-29 20:42 ` Myklebust, Trond
2012-03-29 20:50 ` Dr James Bruce Fields
2012-03-29 20:56 ` Myklebust, Trond
2012-03-29 21:08 ` Dr James Bruce Fields
2012-03-29 21:17 ` Dr James Bruce Fields [this message]
2012-04-05 16:35 ` Orion Poplawski
2012-04-05 16:53 ` Bruce Fields
2012-04-05 20:17 ` Orion Poplawski
2012-04-09 22:32 ` Bruce Fields
2012-04-09 22:58 ` Bruce Fields
2012-03-30 17:12 ` Peter Staubach
2012-03-30 17:20 ` Myklebust, Trond
2012-03-29 20:43 ` Dr James Bruce Fields
2012-03-29 20:50 ` Myklebust, Trond
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=20120329211713.GD21493@fieldses.org \
--to=bfields@fieldses.org \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=orion@cora.nwra.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.