From: Disha Goel <disgoel@linux.ibm.com>
To: brauner@kernel.org, shuah@kernel.org
Cc: linux-fsdevel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, Disha Goel <disgoel@linux.ibm.com>
Subject: [PATCH 2/2] selftests/empty_mntns: use unused bit in unknown_flags_rejected test
Date: Thu, 1 Oct 2026 12:27:28 +0530 [thread overview]
Message-ID: <20261001065728.90239-2-disgoel@linux.ibm.com> (raw)
In-Reply-To: <20261001065728.90239-1-disgoel@linux.ibm.com>
The unknown_flags_rejected test uses 0x800000000ULL (1ULL << 35) to test
that clone3() rejects unknown 64-bit flags with -EINVAL.
However, bit 35 has been allocated to CLONE_NNP, causing clone3() to
succeed and the assertion expecting failure to fail.
Switch to (1ULL << 63) which is an unused high bit so the test
consistently expects -EINVAL.
Fixes: 5b8ffd63fbd9 ("selftests/filesystems: add clone3 tests for empty mount namespaces")
Signed-off-by: Disha Goel <disgoel@linux.ibm.com>
---
.../selftests/filesystems/empty_mntns/clone3_empty_mntns_test.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/filesystems/empty_mntns/clone3_empty_mntns_test.c b/tools/testing/selftests/filesystems/empty_mntns/clone3_empty_mntns_test.c
index de0cbd1a5ee0..b271fed3ae70 100644
--- a/tools/testing/selftests/filesystems/empty_mntns/clone3_empty_mntns_test.c
+++ b/tools/testing/selftests/filesystems/empty_mntns/clone3_empty_mntns_test.c
@@ -868,7 +868,7 @@ TEST(unknown_flags_rejected)
if (pid == 0) {
struct __clone_args args = {
- .flags = 0x800000000ULL,
+ .flags = (1ULL << 63),
.exit_signal = SIGCHLD,
};
pid_t ret;
--
2.45.1
prev parent reply other threads:[~2026-10-01 6:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 6:57 [PATCH 1/2] selftests/empty_mntns: fix header conflicts and remove TOOLS_INCLUDES Disha Goel
2026-10-01 6:57 ` Disha Goel [this message]
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=20261001065728.90239-2-disgoel@linux.ibm.com \
--to=disgoel@linux.ibm.com \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
/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
all inboxes | Powered by JetHome®