From: Avinesh Kumar via ltp <ltp@lists.linux.it>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] syscalls/fsmount02: fix invalid-flags test failure on Linux 7.1+
Date: Thu, 30 Apr 2026 08:33:23 +0200 [thread overview]
Message-ID: <20260430063326.53566-1-avinesh.kumar@suse.com> (raw)
Upstream Linux commit 5e8969bd1927 ("mount: add FSMOUNT_NAMESPACE") [1]
introduced the `FSMOUNT_NAMESPACE` flag, which maps to `0x02`.
This causes fsmount02 test failure as `0x02` value is no longer invalid.
fsmount02.c:56: TFAIL: invalid-flags: fsmount() succeeded unexpectedly (index: 1)
Use `0x80000000` as invalid flag value to adapt test for this upstream change.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5e8969bd1927
Signed-off-by: Avinesh Kumar <avinesh.kumar@suse.com>
---
testcases/kernel/syscalls/fsmount/fsmount02.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/testcases/kernel/syscalls/fsmount/fsmount02.c b/testcases/kernel/syscalls/fsmount/fsmount02.c
index 55f0e2f28..934d775ab 100644
--- a/testcases/kernel/syscalls/fsmount/fsmount02.c
+++ b/testcases/kernel/syscalls/fsmount/fsmount02.c
@@ -19,7 +19,7 @@ static struct tcase {
int exp_errno;
} tcases[] = {
{"invalid-fd", &invalid_fd, FSMOUNT_CLOEXEC, 0, EBADF},
- {"invalid-flags", &fd, 0x02, 0, EINVAL},
+ {"invalid-flags", &fd, 0x80000000, 0, EINVAL},
{"invalid-attrs", &fd, FSMOUNT_CLOEXEC, 0x100, EINVAL},
};
--
2.54.0
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2026-04-30 6:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 6:33 Avinesh Kumar via ltp [this message]
2026-04-30 8:26 ` [LTP] [PATCH] syscalls/fsmount02: fix invalid-flags test failure on Linux 7.1+ Li Wang
2026-04-30 9:14 ` [LTP] " linuxtestproject.agent
2026-05-06 15:49 ` [LTP] [PATCH] " Andrea Cervesato via ltp
2026-05-06 15:49 ` Andrea Cervesato via ltp
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=20260430063326.53566-1-avinesh.kumar@suse.com \
--to=ltp@lists.linux.it \
--cc=avinesh.kumar@suse.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