From: Christian Brauner <christian.brauner@ubuntu.com>
To: Jan Stancek <jstancek@redhat.com>
Cc: Cyril Hrubis <chrubis@suse.cz>,
kernel test robot <rong.a.chen@intel.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Jann Horn <jannh@google.com>, LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org, Aleksa Sarai <cyphar@cyphar.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
ltp@lists.linux.it, Serge Hallyn <serge@hallyn.com>
Subject: Re: [LTP] 303cc571d1: ltp.setns01.fail
Date: Mon, 15 Jun 2020 23:38:43 +0200 [thread overview]
Message-ID: <20200615213843.2ojgm3ob7kp3qq6a@wittgenstein> (raw)
In-Reply-To: <1101600340.15989438.1592229781375.JavaMail.zimbra@redhat.com>
On Mon, Jun 15, 2020 at 10:03:01AM -0400, Jan Stancek wrote:
>
>
> ----- Original Message -----
> > Hi!
> > > setns01 6 TFAIL : setns01.c:176: regular file fd exp_errno=22:
> > > errno=EBADF(9): Bad file descriptor
> > > setns01 0 TINFO : setns(12, 0x20000)
> > > setns01 7 TFAIL : setns01.c:176: regular file fd exp_errno=22:
> > > errno=EBADF(9): Bad file descriptor
> > > setns01 0 TINFO : setns(12, 0x40000000)
> > > setns01 8 TFAIL : setns01.c:176: regular file fd exp_errno=22:
> > > errno=EBADF(9): Bad file descriptor
> > > setns01 0 TINFO : setns(12, 0x20000000)
> > > setns01 9 TFAIL : setns01.c:176: regular file fd exp_errno=22:
> > > errno=EBADF(9): Bad file descriptor
> > > setns01 0 TINFO : setns(12, 0x4000000)
> > > setns01 10 TFAIL : setns01.c:176: regular file fd exp_errno=22:
> > > errno=EBADF(9): Bad file descriptor
> >
> > The messages here are a bit cryptic, I will fix that later on, but what
> > it means here is that the errno has changed from EINVAL to EBADF in a
> > case we pass file descriptor to a regular file to setns().
>
> I posted a series that accepts both errnos about week ago:
> https://lists.linux.it/pipermail/ltp/2020-June/017467.html
When you used to pass an fd that referred to an open file but the file
was not a nsfd the kernel would report EINVAL. Since the pidfd support
this now reports EBADF. While that is a user visible change it is not a
particular worrying one but something we should still fix. Here's the
patch that fixes this:
diff --git a/kernel/nsproxy.c b/kernel/nsproxy.c
index b03df67621d0..cd356630a311 100644
--- a/kernel/nsproxy.c
+++ b/kernel/nsproxy.c
@@ -531,7 +531,7 @@ SYSCALL_DEFINE2(setns, int, fd, int, flags)
} else if (!IS_ERR(pidfd_pid(file))) {
err = check_setns_flags(flags);
} else {
- err = -EBADF;
+ err = -EINVAL;
}
if (err)
goto out;
I'll send a pr for this to Linus this week (or next since I'm on
vacation this week) and get this fixed. Thanks for spotting this. What's
the Reported-by: line format that LTP uses?
Christian
next prev parent reply other threads:[~2020-06-15 21:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 8:58 kernel test robot
2020-06-15 9:18 ` [LTP] " Cyril Hrubis
2020-06-15 14:03 ` Jan Stancek
2020-06-15 21:38 ` Christian Brauner [this message]
2020-06-16 8:08 ` Jan Stancek
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=20200615213843.2ojgm3ob7kp3qq6a@wittgenstein \
--to=christian.brauner@ubuntu.com \
--cc=chrubis@suse.cz \
--cc=cyphar@cyphar.com \
--cc=ebiederm@xmission.com \
--cc=jannh@google.com \
--cc=jstancek@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@lists.01.org \
--cc=ltp@lists.linux.it \
--cc=mtk.manpages@gmail.com \
--cc=rong.a.chen@intel.com \
--cc=serge@hallyn.com \
/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
all inboxes | Powered by JetHome®