From: Omar Sandoval <osandov@osandov.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-api@vger.kernel.org, kernel-team@fb.com,
Xi Wang <xi@cs.washington.edu>
Subject: Re: [RFC PATCH v3 0/2] fs: add AT_REPLACE flag for linkat()
Date: Fri, 4 May 2018 11:29:53 -0700 [thread overview]
Message-ID: <20180504182953.GC26037@vader> (raw)
In-Reply-To: <ba06a3ff-6569-749f-cbc5-f597db65d347@gmail.com>
On Fri, Apr 27, 2018 at 02:00:39PM +0200, Michael Kerrisk (man-pages) wrote:
> Hello Omar,
>
> On 04/24/2018 08:19 AM, Omar Sandoval wrote:
> > From: Omar Sandoval <osandov@fb.com>
> >
> > Hi, Al,
> >
> > This is a respin of my linkat() AT_REPLACE series, previously posted
> > here:
> >
> > https://patchwork.kernel.org/patch/9636735/
> > https://patchwork.kernel.org/patch/9636733/
> >
> > There are no changes since v2, only a rebase onto v4.17-rc2 and some
> > minor additions to the commit messages.
> >
> > The goal is to allow for updating a file atomically in-place with an
> > O_TMPFILE like so:
> >
> > - open temporary file with O_TMPFILE
> > - write temporary file contents
> > - fsync temporary file
> > - atomically replace permanent location with the temporary file
> > - fsync parent directory
>
> Could we have an example program with the next revision please,
> perhaps as part of the commit message?
>
> And, please also some text suitable for inclusion in the linkat(2)
> manual page.
>
> Thanks,
>
> Michael
Yes, I'll do that.
next prev parent reply other threads:[~2018-05-04 18:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 6:19 [RFC PATCH v3 0/2] fs: add AT_REPLACE flag for linkat() Omar Sandoval
2018-04-24 6:19 ` [RFC PATCH v3 1/2] fs: add AT_REPLACE flag for linkat() which replaces the target Omar Sandoval
2018-04-24 22:14 ` Omar Sandoval
2018-04-24 6:19 ` [RFC PATCH v3 2/2] Btrfs: add support for linkat() AT_REPLACE Omar Sandoval
2018-04-24 13:21 ` [RFC PATCH v3 0/2] fs: add AT_REPLACE flag for linkat() Christoph Hellwig
2018-04-24 15:26 ` Omar Sandoval
2018-04-26 7:49 ` Omar Sandoval
2018-04-27 12:00 ` Michael Kerrisk (man-pages)
2018-05-04 18:29 ` Omar Sandoval [this message]
2018-05-04 18:30 ` Omar Sandoval
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=20180504182953.GC26037@vader \
--to=osandov@osandov.com \
--cc=kernel-team@fb.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=xi@cs.washington.edu \
/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.