From: Wei Gao <wegao@suse.com>
To: kernel test robot <oliver.sang@intel.com>
Cc: Andrei Vagin <avagin@google.com>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
lkp@intel.com, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, oe-lkp@lists.linux.dev,
ltp@lists.linux.it
Subject: Re: [LTP] [linus:master] [fs/namespace] 78f0e33cd6: ltp.listmount04.fail
Date: Tue, 25 Nov 2025 10:13:51 +0000 [thread overview]
Message-ID: <aSWBX1urcixS1Fl8@autotest-wegao.qe.prg2.suse.org> (raw)
In-Reply-To: <202511251629.ccc5680d-lkp@intel.com>
On Tue, Nov 25, 2025 at 04:33:35PM +0800, kernel test robot wrote:
>
>
> Hello,
>
> kernel test robot noticed "ltp.listmount04.fail" on:
>
> commit: 78f0e33cd6c939a555aa80dbed2fec6b333a7660 ("fs/namespace: correctly handle errors returned by grab_requested_mnt_ns")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>
> [test failed on linus/master fd95357fd8c6778ac7dea6c57a19b8b182b6e91f]
> [test failed on linux-next/master d724c6f85e80a23ed46b7ebc6e38b527c09d64f5]
>
> in testcase: ltp
> version:
> with following parameters:
>
> disk: 1SSD
> fs: btrfs
> test: syscalls-06/listmount04
>
>
>
> config: x86_64-rhel-9.4-ltp
> compiler: gcc-14
> test machine: 4 threads 1 sockets Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz (Ivy Bridge) with 8G memory
>
> (please refer to attached dmesg/kmsg for entire log/backtrace)
>
>
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <oliver.sang@intel.com>
> | Closes: https://lore.kernel.org/oe-lkp/202511251629.ccc5680d-lkp@intel.com
>
> 2025-11-20 21:35:09 export LTP_RUNTIME_MUL=2
> 2025-11-20 21:35:09 export LTPROOT=/lkp/benchmarks/ltp
> 2025-11-20 21:35:09 kirk -U ltp -f temp_single_test -d /fs/sdb1/tmpdir
> Host information
>
> Hostname: lkp-ivb-d04
> Python: 3.13.5 (main, Jun 25 2025, 18:55:22) [GCC 14.2.0]
> Directory: /fs/sdb1/tmpdir/kirk.root/tmp9k8rfwr2
>
> Connecting to SUT: default
>
> Starting suite: temp_single_test
> ---------------------------------
> ^[[1;37mlistmount04: ^[[0m^[[1;31mfail^[[0m (0.016s)
>
> Execution time: 0.085s
>
> Suite: temp_single_test
> Total runs: 1
> Runtime: 0.016s
> Passed: 7
> Failed: 1
> Skipped: 0
> Broken: 0
> Warnings: 0
> Kernel: Linux 6.18.0-rc1-00119-g78f0e33cd6c9 #1 SMP PREEMPT_DYNAMIC Fri Nov 21 04:59:36 CST 2025
> Machine: unknown
> Arch: x86_64
> RAM: 6900660 kB
> Swap: 0 kB
> Distro: debian 13
>
> Disconnecting from SUT: default
> Session stopped
>
>
>
> The kernel config and materials to reproduce are available at:
> https://download.01.org/0day-ci/archive/20251125/202511251629.ccc5680d-lkp@intel.com
>
>
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
>
>
> --
> Mailing list info: https://lists.linux.it/listinfo/ltp
I guess LTP failed message is "listmount04.c:128: TFAIL: invalid mnt_id_req.spare expected EINVAL: EBADF (9) " ? Since i have not find LTP failure log in this email thread.
Base on kernel change remove spare and add new mnt_ns_fd but LTP listmount04 still set spare.
I suppose LTP case need update base latest change of kernel?
Kernel:
*/
struct mnt_id_req {
__u32 size;
- __u32 spare; <<<<<<<<
+ __u32 mnt_ns_fd; <<<<<<<<
__u64 mnt_id;
__u64 param;
__u64 mnt_ns_id;
LTP case:
{
.req_usage = 1,
.size = MNT_ID_REQ_SIZE_VER0,
.spare = -1, <<<<<<<
.mnt_id = LSMT_ROOT,
.mnt_ids = mnt_ids,
.nr_mnt_ids = MNT_SIZE,
.exp_errno = EINVAL,
.msg = "invalid mnt_id_req.spare",
},
next prev parent reply other threads:[~2025-11-25 10:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 8:33 [linus:master] [fs/namespace] 78f0e33cd6: ltp.listmount04.fail kernel test robot
2025-11-25 10:13 ` Wei Gao [this message]
2025-11-27 1:50 ` [LTP] " Wei Gao
2025-11-27 1:56 ` Oliver Sang
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=aSWBX1urcixS1Fl8@autotest-wegao.qe.prg2.suse.org \
--to=wegao@suse.com \
--cc=avagin@google.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=ltp@lists.linux.it \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.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).