[LTP] [linux-next:master] [mount] 4f5ba37ddc: ltp.fsmount02.fail

[LTP] [linux-next:master] [mount] 4f5ba37ddc: ltp.fsmount02.fail

[kernel test robot]

Hello,

kernel test robot noticed "ltp.fsmount02.fail" on:

commit: 4f5ba37ddcdf5eaac2408178050183345d56b2d3 ("mount: add FSMOUNT_NAMESPACE")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master

[test failed on linux-next/master fd9678829d6dd0c10fde080b536abf4b1121c346]

in testcase: ltp
version: 
with following parameters:

	disk: 1SSD
	fs: f2fs
	test: syscalls-01/fsmount02


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/202602122354.412c5e65-lkp@intel.com


2026-02-10 23:32:32 export LTP_RUNTIME_MUL=2
2026-02-10 23:32:32 export LTPROOT=/lkp/benchmarks/ltp
2026-02-10 23:32:32 kirk -U ltp -f temp_single_test --env TMPDIR=/fs/sda1/tmpdir
Host information

	Hostname:   lkp-ivb-d04
	Python:     3.13.5 (main, Jun 25 2025, 18:55:22) [GCC 14.2.0]
	Directory:  /tmp/kirk.root/tmpcy80fcz_

Connecting to SUT: default

Starting suite: temp_single_test
---------------------------------
^[[1;37mfsmount02: ^[[0m^[[1;31mfail^[[0m | ^[[1;33mtainted^[[0m  (2.116s)
                                                                                                                                
Execution time: 2.187s

	Suite:       temp_single_test
	Total runs:  1
	Runtime:     2.116s
	Passed:      16
	Failed:      8
	Skipped:     0
	Broken:      0
	Warnings:    0
	Kernel:      Linux 6.19.0-rc1-00011-g4f5ba37ddcdf #1 SMP PREEMPT_DYNAMIC Sun Feb  8 10:38:35 CST 2026
	Machine:     unknown
	Arch:        x86_64
	RAM:         6899608 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/20260212/202602122354.412c5e65-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

Re: [LTP] [linux-next:master] [mount] 4f5ba37ddc: ltp.fsmount02.fail

[Cyril Hrubis]

Hi!
> commit: 4f5ba37ddcdf5eaac2408178050183345d56b2d3 ("mount: add FSMOUNT_NAMESPACE")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master

The relevant part of the log is:

fsmount02.c:56: TFAIL: invalid-flags: fsmount() succeeded unexpectedly (index: 1)

This is another case where new flag was added so the invalid flag value
is not invalid anymore. The test needs to be adjusted if/once the patch
hits mainline.

-- 
Cyril Hrubis
chrubis@suse.cz

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

Re: [LTP] [linux-next:master] [mount] 4f5ba37ddc: ltp.fsmount02.fail

[Christian Brauner via ltp]

On Fri, Feb 13, 2026 at 10:35:35AM +0100, Cyril Hrubis wrote:
> Hi!
> > commit: 4f5ba37ddcdf5eaac2408178050183345d56b2d3 ("mount: add FSMOUNT_NAMESPACE")
> > https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
> 
> The relevant part of the log is:
> 
> fsmount02.c:56: TFAIL: invalid-flags: fsmount() succeeded unexpectedly (index: 1)
> 
> This is another case where new flag was added so the invalid flag value
> is not invalid anymore. The test needs to be adjusted if/once the patch
> hits mainline.

Ah, very good to know. Adding Mark so he's aware that this is an
expected failure.

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

Re: [LTP] [linux-next:master] [mount] 4f5ba37ddc: ltp.fsmount02.fail

[Avinesh Kumar via ltp]

Hi,

On 2/14/26 1:24 PM, Christian Brauner via ltp wrote:
> On Fri, Feb 13, 2026 at 10:35:35AM +0100, Cyril Hrubis wrote:
>> Hi!
>>> commit: 4f5ba37ddcdf5eaac2408178050183345d56b2d3 ("mount: add FSMOUNT_NAMESPACE")
>>> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
>> The relevant part of the log is:
>>
>> fsmount02.c:56: TFAIL: invalid-flags: fsmount() succeeded unexpectedly (index: 1)
>>
>> This is another case where new flag was added so the invalid flag value
>> is not invalid anymore. The test needs to be adjusted if/once the patch
>> hits mainline.
FYI, 
https://lore.kernel.org/ltp/20260430063326.53566-1-avinesh.kumar@suse.com/T/#u 

Please review if this is correct solution.

Regards,
Avinesh

> Ah, very good to know. Adding Mark so he's aware that this is an
> expected failure.
>

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp