From: Al Viro <viro@zeniv.linux.org.uk>
To: Amir Goldstein <amir73il@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-unionfs@vger.kernel.org,
Miklos Szeredi <miklos@szeredi.hu>
Subject: Re: [RFC][overlayfs] do we still need d_instantiate_anon() and export of d_alloc_anon()?
Date: Sat, 18 Nov 2023 21:17:33 +0000 [thread overview]
Message-ID: <20231118211733.GG1957730@ZenIV> (raw)
In-Reply-To: <20231118200247.GF1957730@ZenIV>
On Sat, Nov 18, 2023 at 08:02:47PM +0000, Al Viro wrote:
> On Sun, Nov 12, 2023 at 09:26:28AM +0200, Amir Goldstein wrote:
>
> > Tested the patch below.
> > If you want to apply it as part of dcache cleanup, it's fine by me.
> > Otherwise, I will queue it for the next overlayfs update.
>
> OK... Let's do it that way - overlayfs part goes into never-rebased branch
> (no matter which tree), pulled into dcache series and into your overlayfs
> update, with removal of unused stuff done in a separate patch in dcache
> series.
>
> That way we won't step on each other's toes when reordering, etc.
> Does that work for you? I can put the overlayfs part into #no-rebase-overlayfs
> in vfs.git, or you could do it in a v6.7-rc1-based branch in your tree -
> whatever's more convenient for you.
See #no-rebase-overlayfs.
next prev parent reply other threads:[~2023-11-18 21:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-11 8:04 [RFC][overlayfs] do we still need d_instantiate_anon() and export of d_alloc_anon()? Al Viro
2023-11-11 18:31 ` Amir Goldstein
2023-11-11 18:50 ` Al Viro
2023-11-11 20:05 ` Amir Goldstein
2023-11-12 7:26 ` Amir Goldstein
2023-11-18 20:02 ` Al Viro
2023-11-18 21:17 ` Al Viro [this message]
2023-11-19 6:57 ` Amir Goldstein
2023-11-19 7:26 ` Al Viro
2023-11-19 8:19 ` Amir Goldstein
2023-11-20 11:39 ` Amir Goldstein
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=20231118211733.GG1957730@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=amir73il@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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.