From: Christian Brauner <brauner@kernel.org>
To: linux-unionfs@vger.kernel.org
Cc: Miklos Szeredi <miklos@szeredi.hu>,
Amir Goldstein <amir73il@gmail.com>,
Mike Baynton <mike@mbaynton.com>,
linux-fsdevel@vger.kernel.org,
Christian Brauner <brauner@kernel.org>
Subject: [PATCH 0/2] ovl: allow O_PATH file descriptor when specifying layers
Date: Fri, 07 Feb 2025 16:46:38 +0100 [thread overview]
Message-ID: <20250207-work-overlayfs-v1-0-611976e73373@kernel.org> (raw)
Allow overlayfs to use O_PATH file descriptors when specifying layers.
Userspace must currently use non-O_PATH file desriptors which is often
pointless especially if the file descriptors have been created via
open_tree(OPEN_TREE_CLONE). This has been a frequent request and came up
again in [1].
Link: https://lore.kernel.org/r/fd8f6574-f737-4743-b220-79c815ee1554@mbaynton.com [1]
Signed-off-by: Christian Brauner <brauner@kernel.org>
---
Christian Brauner (2):
fs: support O_PATH fds with FSCONFIG_SET_FD
selftests/overlayfs: test specifying layers as O_PATH file descriptors
fs/fs_parser.c | 12 ++--
fs/fsopen.c | 7 ++-
fs/overlayfs/params.c | 10 ++--
include/linux/fs_context.h | 1 +
include/linux/fs_parser.h | 6 +-
.../filesystems/overlayfs/set_layers_via_fds.c | 65 ++++++++++++++++++++++
6 files changed, 87 insertions(+), 14 deletions(-)
---
base-commit: 2014c95afecee3e76ca4a56956a936e23283f05b
change-id: 20250207-work-overlayfs-38fb9156d4c4
next reply other threads:[~2025-02-07 15:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 15:46 Christian Brauner [this message]
2025-02-07 15:46 ` [PATCH 1/2] fs: support O_PATH fds with FSCONFIG_SET_FD Christian Brauner
2025-02-07 17:39 ` Amir Goldstein
2025-02-07 18:09 ` Amir Goldstein
2025-02-10 12:07 ` Christian Brauner
2025-02-07 15:46 ` [PATCH 2/2] selftests/overlayfs: test specifying layers as O_PATH file descriptors Christian Brauner
2025-02-07 18:07 ` 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=20250207-work-overlayfs-v1-0-611976e73373@kernel.org \
--to=brauner@kernel.org \
--cc=amir73il@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=mike@mbaynton.com \
--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