linux-kernel - Re: [LTP] [linus:master] [fs/namespace] 78f0e33cd6: ltp.listmount04.fail

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <aSWBX1urcixS1Fl8@autotest-wegao.qe.prg2.suse.org>
Date: Tue, 25 Nov 2025 10:13:51 +0000
From: Wei Gao <wegao@...e.com>
To: kernel test robot <oliver.sang@...el.com>
Cc: Andrei Vagin <avagin@...gle.com>,
	Christian Brauner <brauner@...nel.org>, Jan Kara <jack@...e.cz>,
	lkp@...el.com, linux-kernel@...r.kernel.org,
	linux-fsdevel@...r.kernel.org, oe-lkp@...ts.linux.dev,
	ltp@...ts.linux.it
Subject: Re: [LTP] [linus:master] [fs/namespace] 78f0e33cd6:
 ltp.listmount04.fail

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@...el.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",
},