From: Petr Vorel <pvorel@suse.cz>
To: Masahiro Yamada <masahiro.yamada@canonical.com>
Cc: Christian Brauner <brauner@kernel.org>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] listmount04: require kernel version 6.11
Date: Mon, 8 Dec 2025 12:23:35 +0100 [thread overview]
Message-ID: <20251208112335.GA683201@pevik> (raw)
In-Reply-To: <20251203081226.1148236-1-masahiro.yamada@canonical.com>
Hi Masahiro,
> On Linux kernel 6.8, the listmount04 test fails as follows:
> Running tests.......
> tst_buffers.c:57: TINFO: Test is using guarded buffers
> tst_test.c:2025: TINFO: LTP version: 20250930
> tst_test.c:2028: TINFO: Tested kernel: 6.8.0 #71 SMP PREEMPT_DYNAMIC Wed Dec 3 16:00:27 JST 2025 x86_64
> tst_kconfig.c:88: TINFO: Parsing kernel config '/proc/config.gz'
> tst_kconfig.c:676: TINFO: CONFIG_TRACE_IRQFLAGS kernel option detected which might slow the execution
> tst_test.c:1846: TINFO: Overall timeout per run is 0h 02m 00s
> listmount04.c:128: TPASS: request points to unaccessible memory : EFAULT (14)
> listmount04.c:128: TPASS: mnt_ids points to unaccessible memory : EFAULT (14)
> listmount04.c:128: TPASS: invalid flags : EINVAL (22)
> listmount04.c:128: TPASS: insufficient mnt_id_req.size : EINVAL (22)
> listmount04.c:128: TPASS: invalid mnt_id_req.spare : EINVAL (22)
> listmount04.c:128: TFAIL: invalid mnt_id_req.param invalid retval 20: SUCCESS (0)
> listmount04.c:128: TFAIL: invalid mnt_id_req.mnt_id expected EINVAL: ENOENT (2)
> listmount04.c:128: TPASS: non-existant mnt_id : ENOENT (2)
> Summary:
> passed 6
> failed 2
> broken 0
> skipped 0
> warnings 0
> INFO: ltp-pan reported some tests FAIL
> LTP Version: 20250930
> INFO: Test end time: Wed Dec 3 07:01:33 UTC 2025
> This test passes only after kernel commit 4bed843b1000 ("fs: reject
> invalid last mount id early"), i.e. kernel version 6.11.
Reviewed-by: Petr Vorel <pvorel@suse.cz>
Good catch.
FYI we have in LTP policy to not hide kernel bugs. But given 4bed843b1000 has
not been merged to stable kernels (checking still supported 6.6 and unsupported
6.11) it's probably considered as a new feature from 6.11-rc1.
@Christian please correct me if I'm wrong.
Kind regards,
Petr
> Signed-off-by: Masahiro Yamada <masahiro.yamada@canonical.com>
> ---
> testcases/kernel/syscalls/listmount/listmount04.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> diff --git a/testcases/kernel/syscalls/listmount/listmount04.c b/testcases/kernel/syscalls/listmount/listmount04.c
> index a52bad064c0e..a6921a24975d 100644
> --- a/testcases/kernel/syscalls/listmount/listmount04.c
> +++ b/testcases/kernel/syscalls/listmount/listmount04.c
> @@ -133,7 +133,7 @@ static void run(unsigned int n)
> static struct tst_test test = {
> .test = run,
> .tcnt = ARRAY_SIZE(tcases),
> - .min_kver = "6.8",
> + .min_kver = "6.11",
> .bufs = (struct tst_buffers []) {
> { &request, .size = MNT_ID_REQ_SIZE_VER0 },
> {},
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-12-08 11:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 8:12 [LTP] [PATCH] listmount04: require kernel version 6.11 Masahiro Yamada via ltp
2025-12-08 11:23 ` Petr Vorel [this message]
2025-12-09 10:12 ` Petr Vorel
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=20251208112335.GA683201@pevik \
--to=pvorel@suse.cz \
--cc=brauner@kernel.org \
--cc=ltp@lists.linux.it \
--cc=masahiro.yamada@canonical.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