selftests/empty_mntns: fix wrong CLONE_EMPTY_MNTNS hex value in comment

CLONE_EMPTY_MNTNS is (1ULL << 37) = 0x2000000000ULL, not 0x400000000ULL.

Fixes: 5b8ffd63fbd9 ("selftests/filesystems: add clone3 tests for empty mount namespaces")
Signed-off-by: Christian Brauner <brauner@kernel.org>

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 d800f661cb7b5839ee12d70d2eb83bd06dcfb0ff..6370086f886df3d7ec8a51fe0e81f9c3c9f1727b 100644 (file)
--- a/tools/testing/selftests/filesystems/empty_mntns/clone3_empty_mntns_test.c
+++ b/tools/testing/selftests/filesystems/empty_mntns/clone3_empty_mntns_test.c
@@ -4,7 +4,7 @@
  *
  * These tests exercise the clone3() code path for creating empty mount
  * namespaces, which is distinct from the unshare() path tested in
- * empty_mntns_test.c.  With clone3(), CLONE_EMPTY_MNTNS (0x400000000ULL)
+ * empty_mntns_test.c.  With clone3(), CLONE_EMPTY_MNTNS (0x2000000000ULL)
  * is a 64-bit flag that implies CLONE_NEWNS.  The implication happens in
  * kernel_clone() before copy_process(), unlike unshare() where it goes
  * through UNSHARE_EMPTY_MNTNS -> CLONE_EMPTY_MNTNS conversion in