From: Christian Brauner <brauner@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: linux-fsdevel@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
Jan Kara <jack@suse.cz>, Jeff Layton <jlayton@kernel.org>,
Amir Goldstein <amir73il@gmail.com>,
Josef Bacik <josef@toxicpanda.com>,
Aleksa Sarai <cyphar@cyphar.com>
Subject: Re: [PATCH 3/7] mount: add FSMOUNT_NAMESPACE
Date: Wed, 11 Feb 2026 13:13:17 +0100 [thread overview]
Message-ID: <20260211-eurem-rinnen-3569a208531b@brauner> (raw)
In-Reply-To: <ad810bc9-5755-416b-a810-5c1019b85b76@sirena.org.uk>
On Wed, Feb 11, 2026 at 11:47:39AM +0000, Mark Brown wrote:
> On Thu, Jan 22, 2026 at 11:48:48AM +0100, Christian Brauner wrote:
> > Add FSMOUNT_NAMESPACE flag to fsmount() that creates a new mount
> > namespace with the newly created filesystem attached to a copy of the
> > real rootfs. This returns a namespace file descriptor instead of an
> > O_PATH mount fd, similar to how OPEN_TREE_NAMESPACE works for open_tree().
>
> I'm seeing a regression in the LTP fsmount02 test in yesterday's -next
> on arm64 which bisect to this patch, the test reports some unexpected
> successes with logs like this:
Thanks. This is postponed until next cycle.
next prev parent reply other threads:[~2026-02-11 12:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 10:48 [PATCH 0/7] fsmount: add FSMOUNT_NAMESPACE Christian Brauner
2026-01-22 10:48 ` [PATCH 1/7] mount: start iterating from start of rbtree Christian Brauner
2026-01-22 10:48 ` [PATCH 2/7] mount: simplify __do_loopback() Christian Brauner
2026-01-22 10:48 ` [PATCH 3/7] mount: add FSMOUNT_NAMESPACE Christian Brauner
2026-02-11 11:47 ` Mark Brown
2026-02-11 12:13 ` Christian Brauner [this message]
2026-03-18 20:16 ` Mark Brown
2026-03-20 13:40 ` Christian Brauner
2026-03-20 14:04 ` Mark Brown
2026-01-22 10:48 ` [PATCH 4/7] tools: update mount.h header Christian Brauner
2026-01-22 10:48 ` [PATCH 5/7] selftests/statmount: add statmount_alloc() helper Christian Brauner
2026-01-22 10:48 ` [PATCH 6/7] selftests: add FSMOUNT_NAMESPACE tests Christian Brauner
2026-01-22 10:48 ` [PATCH 7/7] selftests/open_tree_ns: fix compilation Christian Brauner
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=20260211-eurem-rinnen-3569a208531b@brauner \
--to=brauner@kernel.org \
--cc=amir73il@gmail.com \
--cc=broonie@kernel.org \
--cc=cyphar@cyphar.com \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-fsdevel@vger.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