selftests/landlock: Fix FS tests when run on a private mount point
authorMickaël Salaün <mic@digikod.net>
Sat, 11 May 2024 17:14:37 +0000 (19:14 +0200)
committerMickaël Salaün <mic@digikod.net>
Sat, 11 May 2024 17:18:42 +0000 (19:18 +0200)
commit7e4042abe2ee7c0977fd8bb049a6991b174a5e6f
treecc9ef85764140fd4a51f22565e46b37ccee9b9a9
parent37dc2e0d38d6eb690ee043b43ee6f7cdf2994bf6
selftests/landlock: Fix FS tests when run on a private mount point

According to the test environment, the mount point of the test's working
directory may be shared or not, which changes the visibility of the
nested "tmp" mount point for the test's parent process calling
umount("tmp").

This was spotted while running tests in containers [1], where mount
points are private.

Cc: Günther Noack <gnoack@google.com>
Cc: Shuah Khan <skhan@linuxfoundation.org>
Link: https://github.com/landlock-lsm/landlock-test-tools/pull/4
Fixes: 41cca0542d7c ("selftests/harness: Fix TEST_F()'s vfork handling")
Reviewed-by: Kees Cook <keescook@chromium.org>
Link: https://lore.kernel.org/r/20240511171445.904356-3-mic@digikod.net
Signed-off-by: Mickaël Salaün <mic@digikod.net>
tools/testing/selftests/landlock/fs_test.c