linux-unionfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Christian Brauner <brauner@kernel.org>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	Josef Bacik <josef@toxicpanda.com>,
	 linux-fsdevel@vger.kernel.org, linux-unionfs@vger.kernel.org
Subject: Re: [PATCH RFC v2 2/4] ovl: specify layers via file descriptors
Date: Sat, 12 Oct 2024 10:25:38 +0200	[thread overview]
Message-ID: <CAOQ4uxhhReggva_knvfTfCW4VzgiBo7w3wLMEsp7eLy36cPcfQ@mail.gmail.com> (raw)
In-Reply-To: <20241011-work-overlayfs-v2-2-1b43328c5a31@kernel.org>

On Fri, Oct 11, 2024 at 11:46 PM Christian Brauner <brauner@kernel.org> wrote:
>

nit: if you can avoid using the exact same title for the cover letter and
a patch that would be nice (gmail client collapses them together).

> Currently overlayfs only allows specifying layers through path names.
> This is inconvenient for users such as systemd that want to assemble an
> overlayfs mount purely based on file descriptors.
>
> This enables user to specify both:
>
>     fsconfig(fd_overlay, FSCONFIG_SET_FD, "upperdir+", NULL, fd_upper);
>     fsconfig(fd_overlay, FSCONFIG_SET_FD, "workdir+",  NULL, fd_work);
>     fsconfig(fd_overlay, FSCONFIG_SET_FD, "lowerdir+", NULL, fd_lower1);
>     fsconfig(fd_overlay, FSCONFIG_SET_FD, "lowerdir+", NULL, fd_lower2);
>
> in addition to:
>
>     fsconfig(fd_overlay, FSCONFIG_SET_STRING, "upperdir+", "/upper",  0);
>     fsconfig(fd_overlay, FSCONFIG_SET_STRING, "workdir+",  "/work",   0);
>     fsconfig(fd_overlay, FSCONFIG_SET_STRING, "lowerdir+", "/lower1", 0);
>     fsconfig(fd_overlay, FSCONFIG_SET_STRING, "lowerdir+", "/lower2", 0);
>

Please add a minimal example with FSCONFIG_SET_FD to overlayfs.rst.
I am not looking for a user manual, just one example to complement the
FSCONFIG_SET_STRING examples.

I don't mind adding config types on a per need basis, but out of curiosity
do you think the need will arise to support FSCONFIG_SET_PATH{,_EMPTY}
in the future? It is going to be any more challenging than just adding
support for
just FSCONFIG_SET_FD?

Again, not asking you to do extra work for a feature that no user asked for.

Other than that, it looks very nice and useful.

Thanks,
Amir.

  parent reply	other threads:[~2024-10-12  8:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-11 21:45 [PATCH RFC v2 0/4] ovl: specify layers via file descriptors Christian Brauner
2024-10-11 21:45 ` [PATCH RFC v2 1/4] fs: add helper to use mount option as path or fd Christian Brauner
2024-10-12  7:21   ` Amir Goldstein
2024-10-12  8:20     ` Amir Goldstein
2024-10-14  8:20       ` Christian Brauner
2024-10-11 21:45 ` [PATCH RFC v2 2/4] ovl: specify layers via file descriptors Christian Brauner
2024-10-11 22:27   ` Al Viro
2024-10-12  8:25   ` Amir Goldstein [this message]
2024-10-12 10:37     ` Christian Brauner
2024-10-13 14:54       ` Amir Goldstein
2024-10-11 21:45 ` [PATCH RFC v2 3/4] selftests: use shared header Christian Brauner
2024-10-12  7:33   ` Amir Goldstein
2024-10-11 21:45 ` [PATCH RFC v2 4/4] selftests: add overlayfs fd mounting selftests Christian Brauner
2024-10-12  7:18   ` 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=CAOQ4uxhhReggva_knvfTfCW4VzgiBo7w3wLMEsp7eLy36cPcfQ@mail.gmail.com \
    --to=amir73il@gmail.com \
    --cc=brauner@kernel.org \
    --cc=josef@toxicpanda.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 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).