[LTP] [PATCH] syscalls/fsmount02: fix invalid-flags test failure on Linux 7.1+
Avinesh Kumar
avinesh.kumar@suse.com
Thu Apr 30 08:33:23 CEST 2026
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
More information about the ltp
mailing list