From: "Anna Schumaker" <anna@kernel.org>
To: "Christian Brauner" <brauner@kernel.org>,
"Jeff Layton" <jlayton@kernel.org>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org,
"Trond Myklebust" <trondmy@kernel.org>,
"Alexander Viro" <viro@zeniv.linux.org.uk>,
"Jan Kara" <jack@suse.cz>,
"Seth Forshee (DigitalOcean)" <sforshee@kernel.org>,
"Alexander Mikhalitsyn" <alexander@mihalicyn.com>
Subject: Re: [PATCH] vfs: add FS_USERNS_DELEGATABLE flag and set it for NFS
Date: Tue, 03 Feb 2026 10:41:52 -0500 [thread overview]
Message-ID: <b9e9b0dd-745b-46fb-9e62-807d53dd417c@app.fastmail.com> (raw)
In-Reply-To: <20260203-leimen-kundgeben-7be98e9cd156@brauner>
On Tue, Feb 3, 2026, at 10:08 AM, Christian Brauner wrote:
> On Thu, 29 Jan 2026 16:47:43 -0500, Jeff Layton wrote:
>> Commit e1c5ae59c0f2 ("fs: don't allow non-init s_user_ns for filesystems
>> without FS_USERNS_MOUNT") prevents the mount of any filesystem inside a
>> container that doesn't have FS_USERNS_MOUNT set.
>>
>> This broke NFS mounts in our containerized environment. We have a daemon
>> somewhat like systemd-mountfsd running in the init_ns. A process does a
>> fsopen() inside the container and passes it to the daemon via unix
>> socket.
>>
>> [...]
>
> Applied to the vfs-7.0.misc branch of the vfs/vfs.git tree.
> Patches in the vfs-7.0.misc branch should appear in linux-next soon.
>
> Please report any outstanding bugs that were missed during review in a
> new review to the original patch series allowing us to drop it.
>
> It's encouraged to provide Acked-bys and Reviewed-bys even though the
> patch has now been applied. If possible patch trailers will be updated.
Acked-by: Anna Schumaker <anna.schumaker@oracle.com>
>
> Note that commit hashes shown below are subject to change due to rebase,
> trailer updates or similar. If in doubt, please check the listed branch.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
> branch: vfs-7.0.misc
>
> [1/1] vfs: add FS_USERNS_DELEGATABLE flag and set it for NFS
> https://git.kernel.org/vfs/vfs/c/269c46e936f3
next prev parent reply other threads:[~2026-02-03 15:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 21:47 [PATCH] vfs: add FS_USERNS_DELEGATABLE flag and set it for NFS Jeff Layton
2026-02-03 15:08 ` Christian Brauner
2026-02-03 15:41 ` Anna Schumaker [this message]
2026-06-09 10:57 ` Jeff Layton
2026-02-03 16:11 ` Alexander Mikhalitsyn
2026-02-03 16:21 ` Jeff Layton
2026-02-03 16:41 ` Christian Brauner
2026-02-03 16:45 ` Alexander Mikhalitsyn
2026-06-08 20:08 ` Jeff Layton
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=b9e9b0dd-745b-46fb-9e62-807d53dd417c@app.fastmail.com \
--to=anna@kernel.org \
--cc=alexander@mihalicyn.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=sforshee@kernel.org \
--cc=trondmy@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