From: David Howells <dhowells@redhat.com>
To: Omar Sandoval <osandov@osandov.com>
Cc: dhowells@redhat.com, "Colin Walters" <walters@verbum.org>,
"Al Viro" <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, "Christoph Hellwig" <hch@lst.de>,
"Theodore Ts'o" <tytso@mit.edu>,
adilger.kernel@dilger.ca,
"Darrick J. Wong" <darrick.wong@oracle.com>,
"Chris Mason" <clm@fb.com>,
josef@toxicpanda.com, dsterba@suse.com,
linux-ext4 <linux-ext4@vger.kernel.org>,
xfs <linux-xfs@vger.kernel.org>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Making linkat() able to overwrite the target
Date: Fri, 17 Jan 2020 11:42:55 +0000 [thread overview]
Message-ID: <359591.1579261375@warthog.procyon.org.uk> (raw)
In-Reply-To: <2397bb4a-2ca2-4b44-8c79-64efba9aa04d@www.fastmail.com>
Hi Omar,
Do you still have your AT_REPLACE patches? You said that you'd post a v4
series, though I don't see it. I could make use of such a feature in
cachefiles inside the kernel. For my original question, see:
https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=fscache-iter
And do you have ext4 support for it?
Colin Walters <walters@verbum.org> wrote:
> On Tue, Jan 14, 2020, at 1:06 PM, David Howells wrote:
>
> > Yes, I suggested AT_LINK_REPLACE as said magical flag.
>
> This came up before right?
>
> https://lore.kernel.org/linux-fsdevel/cover.1524549513.git.osandov@fb.com/
David
next prev parent reply other threads:[~2020-01-17 11:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 16:34 Making linkat() able to overwrite the target David Howells
2020-01-14 17:02 ` Al Viro
2020-01-14 18:06 ` David Howells
2020-01-14 19:37 ` Miklos Szeredi
2020-01-17 0:46 ` Colin Walters
2020-01-17 9:57 ` Amir Goldstein
2020-01-17 11:42 ` David Howells [this message]
2020-01-17 16:22 ` Omar Sandoval
2020-01-17 16:39 ` David Howells
2020-01-15 8:36 ` Christoph Hellwig
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=359591.1579261375@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=adilger.kernel@dilger.ca \
--cc=clm@fb.com \
--cc=darrick.wong@oracle.com \
--cc=dsterba@suse.com \
--cc=hch@lst.de \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=osandov@osandov.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=walters@verbum.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).