From: Cyril Hrubis <chrubis@suse.cz>
To: kernel test robot <rong.a.chen@intel.com>
Cc: Christian Brauner <christian.brauner@ubuntu.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>,
Serge Hallyn <serge@hallyn.com>,
ltp@lists.linux.it, "Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [LTP] 303cc571d1: ltp.setns01.fail
Date: Mon, 15 Jun 2020 11:18:50 +0200 [thread overview]
Message-ID: <20200615091850.GA3373@yuki.lan> (raw)
In-Reply-To: <20200615085836.GR12456@shao2-debian>
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().
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2020-06-15 9:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 8:58 303cc571d1: ltp.setns01.fail kernel test robot
2020-06-15 9:18 ` Cyril Hrubis [this message]
2020-06-15 14:03 ` [LTP] " Jan Stancek
2020-06-15 21:38 ` Christian Brauner
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=20200615091850.GA3373@yuki.lan \
--to=chrubis@suse.cz \
--cc=christian.brauner@ubuntu.com \
--cc=cyphar@cyphar.com \
--cc=ebiederm@xmission.com \
--cc=jannh@google.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;
as well as URLs for NNTP newsgroup(s).