From: Miklos Szeredi <miklos@szeredi.hu>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Miklos Szeredi <mszeredi@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
overlayfs <linux-unionfs@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Andreas Gruenbacher <agruenba@redhat.com>
Subject: Re: [PATCH v2 0/2] allow overlayfs to do RCU lookups
Date: Wed, 18 Aug 2021 17:03:27 +0200 [thread overview]
Message-ID: <CAJfpegsSQv5im4KRN3EfryyNy6aq9eRPPgL_K-1Knj+qtXiaQg@mail.gmail.com> (raw)
In-Reply-To: <YR0YiSP3DliPCPWF@zeniv-ca.linux.org.uk>
On Wed, 18 Aug 2021 at 16:27, Al Viro <viro@zeniv.linux.org.uk> wrote:
>
> On Wed, Aug 18, 2021 at 03:33:58PM +0200, Miklos Szeredi wrote:
> > I'd really like to fix this in some form, but not getting any response
> > [1][2][3].
> >
> > Al, Linus, can you please comment?
> >
> > I'm happy to take this through the overlayfs tree, just need an ACK for the
> > VFS API change.
>
> Looks reasonable enough; I'm not too happy about yet another place LOOKUP_...
> details get tangled into, though. Do we want it to be more than just a
> bool rcu?
I'd be fine with that change. Calling with false/true is less
descriptive than calling with 0/LOOKUP_RCU but I guess we can leave
the actual calls to use the latter?
Thanks,
Miklos
prev parent reply other threads:[~2021-08-18 15:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 13:33 [PATCH v2 0/2] allow overlayfs to do RCU lookups Miklos Szeredi
2021-08-18 13:33 ` [PATCH v2 1/2] vfs: add flags argument to ->get_acl() callback Miklos Szeredi
2021-08-18 13:49 ` Christian Brauner
2021-08-18 13:34 ` [PATCH v2 2/2] ovl: enable RCU'd ->get_acl() Miklos Szeredi
2021-08-18 18:34 ` Linus Torvalds
2021-08-18 18:53 ` Miklos Szeredi
2021-08-18 14:26 ` [PATCH v2 0/2] allow overlayfs to do RCU lookups Al Viro
2021-08-18 15:03 ` Miklos Szeredi [this message]
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=CAJfpegsSQv5im4KRN3EfryyNy6aq9eRPPgL_K-1Knj+qtXiaQg@mail.gmail.com \
--to=miklos@szeredi.hu \
--cc=agruenba@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=mszeredi@redhat.com \
--cc=torvalds@linux-foundation.org \
--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 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).