From: bfields@fieldses.org (J. Bruce Fields)
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Drew DeVault <sir@cmpwn.com>,
linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org,
Aleksa Sarai <cyphar@cyphar.com>
Subject: Re: [RFC PATCH] fs: introduce mkdirat2 syscall for atomic mkdir
Date: Mon, 1 Mar 2021 14:02:59 -0500 [thread overview]
Message-ID: <20210301190259.GC14881@fieldses.org> (raw)
In-Reply-To: <YDsGzhBzLzSp6nPj@zeniv-ca.linux.org.uk>
On Sun, Feb 28, 2021 at 02:58:22AM +0000, Al Viro wrote:
> TBH, I don't understand what are you trying to achieve -
> what will that mkdir+open combination buy you, especially
> since that atomicity goes straight out of window if you try
> to use that on e.g. NFS. How is the userland supposed to make
> use of that thing?
For what it's worth, the RPC that creates a directory can also get a
filehandle of the new directory, so I don't think there's anything in
the NFS protocol that would *prevent* implementing this. (Whether
that's useful, I don't know.)
--b.
next prev parent reply other threads:[~2021-03-01 19:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-28 0:25 [RFC PATCH] fs: introduce mkdirat2 syscall for atomic mkdir Drew DeVault
2021-02-28 2:13 ` Al Viro
2021-02-28 2:21 ` Drew DeVault
2021-02-28 2:58 ` Al Viro
2021-02-28 13:56 ` Drew DeVault
2021-03-01 19:02 ` J. Bruce Fields [this message]
2021-03-08 13:50 ` Stefan Metzmacher
2021-02-28 2:24 ` Matthew Wilcox
2021-02-28 2:26 ` Drew DeVault
2021-02-28 4:03 ` Matthew Wilcox
2021-02-28 13:57 ` Drew DeVault
2021-03-01 19:09 ` J. Bruce Fields
2021-03-01 19:35 ` Matthew Wilcox
2021-03-01 20:10 ` J. Bruce Fields
2021-03-02 8:24 ` Miklos Szeredi
2021-03-02 7:13 ` Amir Goldstein
2021-03-03 2:39 ` Aleksa Sarai
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=20210301190259.GC14881@fieldses.org \
--to=bfields@fieldses.org \
--cc=cyphar@cyphar.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sir@cmpwn.com \
--cc=viro@zeniv.linux.org.uk \
/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.