From: Amir Goldstein <amir73il@gmail.com>
To: Christian Brauner <brauner@kernel.org>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
linux-fsdevel@vger.kernel.org, linux-unionfs@vger.kernel.org
Subject: Re: [PATCH v2 0/2] ovl: port to new mount api & updated layer parsing
Date: Fri, 9 Jun 2023 22:30:24 +0300 [thread overview]
Message-ID: <CAOQ4uxhw9PLz7JaLaZR4hidZUEod2fkiVWvkmbZQoFaiMNe2XQ@mail.gmail.com> (raw)
In-Reply-To: <20230605-fs-overlayfs-mount_api-v2-0-3da91c97e0c0@kernel.org>
On Fri, Jun 9, 2023 at 6:42 PM Christian Brauner <brauner@kernel.org> wrote:
>
> Hey everyone,
>
> This ports overlayfs to the new mount api and modifies layer parsing to
> allow for additive layer specification via fsconfig().
>
> I'm not sure if I need to rebase the changes on top of Amir's lazy
> lookup. If so, please let me know!
Yes, please.
I look at the conflicts and they don't look so bad.
I think only need to figure out numlowerdata during parsing
which should be pretty easy and then the entire wacky loop
to figure out numlowerdata in ovl_get_lowerstack() can be nuked.
all the rest stays the same.
Thanks,
Amir.
prev parent reply other threads:[~2023-06-09 19:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 15:41 [PATCH v2 0/2] ovl: port to new mount api & updated layer parsing Christian Brauner
2023-06-09 15:41 ` [PATCH v2 1/2] ovl: port to new mount api Christian Brauner
2023-06-09 16:09 ` Colin Walters
2023-06-10 7:18 ` Christian Brauner
2023-06-09 19:25 ` Amir Goldstein
2023-06-10 7:15 ` Christian Brauner
2023-06-09 15:41 ` [PATCH v2 2/2] ovl: modify layer parameter parsing Christian Brauner
2023-06-09 19:52 ` Amir Goldstein
2023-06-10 7:13 ` Christian Brauner
2023-06-09 19:30 ` Amir Goldstein [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=CAOQ4uxhw9PLz7JaLaZR4hidZUEod2fkiVWvkmbZQoFaiMNe2XQ@mail.gmail.com \
--to=amir73il@gmail.com \
--cc=brauner@kernel.org \
--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 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).