From: Christian Brauner <brauner@kernel.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Yang Xu <xuyang2018.jy@fujitsu.com>,
overlayfs <linux-unionfs@vger.kernel.org>,
Seth Forshee <sforshee@kernel.org>
Subject: Re: [PATCH v2] overlayfs: improve ovl_get_acl
Date: Thu, 28 Jul 2022 16:23:19 +0200 [thread overview]
Message-ID: <20220728142319.ddww4jrt7ighcj5y@wittgenstein> (raw)
In-Reply-To: <CAJfpegvyhaUAbVYmkAwfkrgsAeauU54GxMWt4fD89TB-zAGXWg@mail.gmail.com>
On Thu, Jul 28, 2022 at 03:06:21PM +0200, Miklos Szeredi wrote:
> On Thu, 28 Jul 2022 at 03:48, Yang Xu <xuyang2018.jy@fujitsu.com> wrote:
> >
> > Provide a proper stub for the !CONFIG_FS_POSIX_ACL case.
>
> Applied, thanks.
Hey Miklos,
Just an fyi that this will likely introduce a (somewhat minor) merge
conflict with the series to fix POSIX ACLs with overlayfs on top of
idmapped layers that I mentioned to you a few weeks ago in [1].
The series is - as announced in the mail above - in [2] and been in next
for quite a while now.
It's right before the mw so ideally I wouldn't want to rebase. Let me
know if I you want me to do anything. Ideally you could probably just
wait until I sent the PR next week.
Thanks!
Christian
[1]: https://lore.kernel.org/linux-unionfs/20220713101814.d5vg3qcc2qk46vqs@wittgenstein/raw
[2]: https://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux.git/log/?h=fs.idmapped.overlay.acl
next prev parent reply other threads:[~2022-07-28 14:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 2:49 [PATCH v2] overlayfs: improve ovl_get_acl Yang Xu
2022-07-28 13:06 ` Miklos Szeredi
2022-07-28 14:23 ` Christian Brauner [this message]
2022-08-02 13:46 ` Miklos Szeredi
2022-08-03 7:43 ` Christian Brauner
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=20220728142319.ddww4jrt7ighcj5y@wittgenstein \
--to=brauner@kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=sforshee@kernel.org \
--cc=xuyang2018.jy@fujitsu.com \
/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).