From: Carlos Llamas <cmllamas@google.com>
To: Andrei Vagin <avagin@gmail.com>
Cc: Mark Brown <broonie@kernel.org>, Andrei Vagin <avagin@google.com>,
Christian Brauner <brauner@kernel.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>, Jan Kara <jack@suse.cz>,
Andrea Cervesato <andrea.cervesato@suse.com>
Subject: Re: [PATCH] fs/namespace: correctly handle errors returned by grab_requested_mnt_ns
Date: Mon, 24 Nov 2025 19:28:25 +0000 [thread overview]
Message-ID: <aSSx2YDHAbcOhgZ0@google.com> (raw)
In-Reply-To: <CANaxB-z2hJ3xT7ViA1ERkgFQMaHThgriK_+goMyoNeDtrFBpcQ@mail.gmail.com>
On Mon, Nov 24, 2025 at 11:14:46AM -0800, Andrei Vagin wrote:
> On Mon, Nov 24, 2025 at 3:23 AM Mark Brown <broonie@kernel.org> wrote:
> >
> > On Sun, Nov 23, 2025 at 07:15:16AM -0800, Andrei Vagin wrote:
> > > On Sun, Nov 23, 2025 at 4:51 AM Mark Brown <broonie@kernel.org> wrote:
> >
> > > > listmount04.c:128: TFAIL: invalid mnt_id_req.spare expected EINVAL: EBADF (9)
> >
> > > The merged patch is slightly different from what you can see on the
> > > mailing list, so it's better to look at commit 78f0e33cd6c93
> > > ("fs/namespace: correctly handle errors returned by
> > > grab_requested_mnt_ns") to understand what is going on here.
> >
> > > With this patch, the spare field can be used as the `mnt_ns_fd`. EINVAL
> > > is returned if both mnt_ns_fd and mnt_ns_id are set. A non-zero
> > > mnt_ns_fd (the old spare) is interpreted as a namespace file descriptor.
> >
> > I can see what's happening - the question is if the test failure it
> > triggers is a problem in the kernel or in the test.
>
> This is a test problem. The test has to be modified to check cases when
> the target mount namespace is specified by mnt_fs_fd.
Cc: Andrea Cervesato <andrea.cervesato@suse.com>
Loop in Andrea (test owner) to possibly make the corresponding updates.
Thanks,
Carlos Llamas
prev parent reply other threads:[~2025-11-24 19:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 6:28 [PATCH] fs/namespace: correctly handle errors returned by grab_requested_mnt_ns Andrei Vagin
2025-11-11 8:21 ` Jan Kara
2025-11-11 9:13 ` Christian Brauner
2025-11-11 16:20 ` Andrei Vagin
2025-11-12 9:42 ` Christian Brauner
2025-11-23 12:51 ` Mark Brown
2025-11-23 15:15 ` Andrei Vagin
2025-11-24 11:23 ` Mark Brown
2025-11-24 19:14 ` Andrei Vagin
2025-11-24 19:28 ` Carlos Llamas [this message]
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=aSSx2YDHAbcOhgZ0@google.com \
--to=cmllamas@google.com \
--cc=andrea.cervesato@suse.com \
--cc=avagin@gmail.com \
--cc=avagin@google.com \
--cc=brauner@kernel.org \
--cc=broonie@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).