From: "John Ericson" <mail@johnericson.me>
To: "Andy Lutomirski" <luto@kernel.org>,
"Christian Brauner" <brauner@kernel.org>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
"Jann Horn" <jannh@google.com>,
linux-api <linux-api@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>, "Kees Cook" <kees@kernel.org>,
"Farid Zakaria" <farid.m.zakaria@gmail.com>,
"Al Viro" <viro@zeniv.linux.org.uk>, "Jan Kara" <jack@suse.cz>,
LKML <linux-kernel@vger.kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
linux-doc <linux-doc@vger.kernel.org>
Subject: Re: [PATCH RFC 4/7] fs: support FD_FAILFS_ROOT in fchroot()
Date: Sun, 26 Jul 2026 23:30:29 -0400 [thread overview]
Message-ID: <09b4735f-c04e-40f3-a7f5-254b7918fbfd@app.fastmail.com> (raw)
In-Reply-To: <CALCETrW-ObgCm=Vhm6AiyyS25q+SyXkCvVWB7JEaawmOMCrrpA@mail.gmail.com>
Very happy to see this patch series appear; thanks Christian!
Also happy with where this specific thread is going. I will just add
that an additional flag in fs_struct to force RESOLVE_BENEATH in *all* path
lookup would also be nice. The combination of:
root = pwd = failfs;
chroot_locked = false;
always_resolve_beneath = true;
goes along way to getting Capsicum's "capability mode". Then we just
need to figure out things like more capabilities for directory file
descriptors per Andy's brainstorming thread thread (which I ought to get
to replying to).
John
next prev parent reply other threads:[~2026-07-27 3:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 11:30 [PATCH RFC 0/7] fs: add failfs Christian Brauner
2026-07-23 11:30 ` [PATCH RFC 1/7] " Christian Brauner
2026-07-23 11:30 ` [PATCH RFC 2/7] fs: add FD_FAILFS_ROOT and support it in fchdir() Christian Brauner
2026-07-23 11:30 ` [PATCH RFC 3/7] fs: add fchroot() Christian Brauner
2026-07-23 11:30 ` [PATCH RFC 4/7] fs: support FD_FAILFS_ROOT in fchroot() Christian Brauner
2026-07-23 12:49 ` Andy Lutomirski
2026-07-23 13:01 ` Christian Brauner
2026-07-23 13:50 ` Andy Lutomirski
2026-07-23 14:35 ` Christian Brauner
2026-07-23 16:59 ` Andy Lutomirski
2026-07-27 3:30 ` John Ericson [this message]
2026-07-27 7:42 ` Andy Lutomirski
2026-07-27 7:57 ` Andy Lutomirski
2026-07-27 8:59 ` Christian Brauner
2026-07-27 10:23 ` Andy Lutomirski
2026-07-23 14:42 ` Jann Horn
2026-07-23 14:07 ` Jann Horn
2026-07-23 16:56 ` Andy Lutomirski
2026-07-23 11:30 ` [PATCH RFC 5/7] arch: hookup fchroot() system call Christian Brauner
2026-07-23 11:30 ` [PATCH RFC 6/7] selftests/filesystems: add failfs selftests Christian Brauner
2026-07-23 11:30 ` [PATCH RFC 7/7] Documentation: add failfs documentation Christian Brauner
2026-07-23 14:04 ` Miquel Sabaté Solà
2026-07-23 12:53 ` [PATCH RFC 0/7] fs: add failfs Andy Lutomirski
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=09b4735f-c04e-40f3-a7f5-254b7918fbfd@app.fastmail.com \
--to=mail@johnericson.me \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=farid.m.zakaria@gmail.com \
--cc=hpa@zytor.com \
--cc=jack@suse.cz \
--cc=jannh@google.com \
--cc=kees@kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.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