From: Cyril Hrubis <chrubis@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: Linux Test Project <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH STAGING v4 12/16] fchroot09: test setns escape from failfs root
Date: Wed, 14 Oct 2026 13:52:30 +0200 [thread overview]
Message-ID: <as9s_vmNm66HStbG@yuki.lan> (raw)
In-Reply-To: <20260831-fchroot-v4-12-57cceb68f927@suse.com>
Hi!
> Verify that entering failfs with fchroot() is hard to undo: a process
> inside counts as chrooted, so the remaining way out is a pre-opened
> mount namespace fd. setns() into it resets both the root and the
> working directory.
>
> Signed-off-by: Andrea Cervesato <andrea.cervesato@suse.com>
> ---
> runtest/staging | 1 +
> testcases/kernel/syscalls/fchroot/.gitignore | 1 +
> testcases/kernel/syscalls/fchroot/fchroot09.c | 86 +++++++++++++++++++++++++++
> 3 files changed, 88 insertions(+)
>
> diff --git a/runtest/staging b/runtest/staging
> index 8dfe95c4a..23f6c6a20 100644
> --- a/runtest/staging
> +++ b/runtest/staging
> @@ -8,3 +8,4 @@ fchroot05 fchroot05
> fchroot06 fchroot06
> fchroot07 fchroot07
> fchroot08 fchroot08
> +fchroot09 fchroot09
> diff --git a/testcases/kernel/syscalls/fchroot/.gitignore b/testcases/kernel/syscalls/fchroot/.gitignore
> index 0a2510d8a..b577da61f 100644
> --- a/testcases/kernel/syscalls/fchroot/.gitignore
> +++ b/testcases/kernel/syscalls/fchroot/.gitignore
> @@ -7,3 +7,4 @@ fchroot06
> fchroot07
> fchroot07_child
> fchroot08
> +fchroot09
> diff --git a/testcases/kernel/syscalls/fchroot/fchroot09.c b/testcases/kernel/syscalls/fchroot/fchroot09.c
> new file mode 100644
> index 000000000..bc9324ceb
> --- /dev/null
> +++ b/testcases/kernel/syscalls/fchroot/fchroot09.c
> @@ -0,0 +1,86 @@
> +// SPDX-License-Identifier: GPL-2.0-or-later
> +/*
> + * Copyright (C) 2026 SUSE LLC Andrea Cervesato <andrea.cervesato@suse.com>
> + */
> +
> +/*\
> + * Test that :manpage:`setns(2)` escapes the failfs root.
> + *
> + * Entering failfs with :manpage:`fchroot(2)` is hard to undo: a process
> + * inside counts as chrooted, so :manpage:`chroot(2)` and :manpage:`fchroot(2)`
> + * back out require ``CAP_SYS_CHROOT``. The remaining way out is a pre-opened
> + * mount namespace file descriptor: :manpage:`setns(2)` into it resets both the
> + * root and the working directory.
> + *
> + * Root is required because entering failfs requires ``CAP_SYS_CHROOT`` and
> + * :manpage:`setns(2)` into the mount namespace requires ``CAP_SYS_ADMIN``.
> + *
> + * The test runs in a forked child so the root of the parent process is
> + * left untouched.
> + */
> +
> +#define _GNU_SOURCE
> +#include <fcntl.h>
> +#include <sys/stat.h>
> +#include "tst_test.h"
> +#include "lapi/fcntl.h"
> +#include "lapi/sched.h"
> +#include "lapi/setns.h"
> +#include "lapi/syscalls.h"
> +
> +#define ABSDIR "abs"
> +
> +static void run(void)
> +{
> + if (SAFE_FORK())
> + return;
> +
> + struct stat realroot, st;
> + int nsfd;
> +
> + SAFE_STAT("/", &realroot);
> + nsfd = SAFE_OPEN("/proc/self/ns/mnt", O_RDONLY);
> +
> + TST_EXP_PASS(tst_syscall(__NR_fchroot, FD_FAILFS_ROOT, 0),
> + "fchroot() with the FD_FAILFS_ROOT sentinel");
> +
> + TST_EXP_FAIL2(open(ABSDIR, O_PATH), EOPNOTSUPP,
> + "absolute lookup after entering failfs");
> +
> + TST_EXP_PASS(setns(nsfd, CLONE_NEWNS),
> + "setns() back into the mount namespace");
> +
> + SAFE_CLOSE(nsfd);
> +
> + SAFE_STAT("/", &st);
> + TST_EXP_EXPR(st.st_dev == realroot.st_dev &&
> + st.st_ino == realroot.st_ino,
> + "root restored after setns()");
> +
> + SAFE_STAT(".", &st);
> + TST_EXP_EXPR(st.st_dev == realroot.st_dev &&
> + st.st_ino == realroot.st_ino,
> + "working directory restored after setns()");
> +
> + exit(0);
Here as well, no need for the exit.
> +}
> +
> +static void setup(void)
> +{
> + char *tmpdir;
> + char abs_path[PATH_MAX];
> +
> + tmpdir = tst_tmpdir_path();
> + snprintf(abs_path, sizeof(abs_path), "%s/%s", tmpdir, "target");
> +
> + SAFE_TOUCH("target", 0644, NULL);
> + SAFE_SYMLINK(abs_path, ABSDIR);
Here as well, why are all the absolute directories symlinks? It makes
sense to have a test symlink to absolute directory restarts the lookup
and fails, but why don't we use just abs_path in most of the tests?
I suppose that we can even open just "/" with O_PATH to check if the
failfs root is active or not...
> +}
> +
> +static struct tst_test test = {
> + .test_all = run,
> + .setup = setup,
> + .needs_root = 1,
> + .forks_child = 1,
> + .needs_tmpdir = 1,
> +};
>
> --
> 2.51.0
>
>
> --
> Mailing list info: https://lists.linux.it/listinfo/ltp
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-10-14 11:52 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 8:00 [LTP] [PATCH v4 00/16] fchroot: add fchroot() testing suite Andrea Cervesato
2026-08-31 8:00 ` [LTP] [PATCH v4 01/16] syscalls: add v7.3 syscall numbers Andrea Cervesato
2026-08-31 8:00 ` [LTP] [PATCH v4 02/16] syscalls: update outdated syscall entries Andrea Cervesato
2026-08-31 8:00 ` [LTP] [PATCH STAGING v4 03/16] lapi: fallback fchroot() parameters Andrea Cervesato
2026-08-31 8:00 ` [LTP] [PATCH STAGING v4 04/16] fchroot01: test fchroot() with a directory fd Andrea Cervesato
2026-08-31 9:06 ` [LTP] syscalls: add v7.3 syscall numbers linuxtestproject.agent
2026-10-12 10:25 ` [LTP] [PATCH STAGING v4 04/16] fchroot01: test fchroot() with a directory fd Cyril Hrubis
2026-08-31 8:00 ` [LTP] [PATCH STAGING v4 05/16] fchroot02: test fchroot() invalid arguments Andrea Cervesato
2026-10-12 10:51 ` Cyril Hrubis
2026-08-31 8:00 ` [LTP] [PATCH STAGING v4 06/16] fchroot03: test fchroot() permission checks Andrea Cervesato
2026-10-12 10:32 ` Cyril Hrubis
2026-08-31 8:00 ` [LTP] [PATCH STAGING v4 07/16] fchroot04: test fchroot() into failfs as root Andrea Cervesato
2026-10-12 11:03 ` Cyril Hrubis
2026-08-31 8:00 ` [LTP] [PATCH STAGING v4 08/16] fchroot05: test failfs root can not be referenced Andrea Cervesato
2026-10-12 11:14 ` Cyril Hrubis
2026-08-31 8:00 ` [LTP] [PATCH STAGING v4 09/16] fchroot06: test path walks under failfs root Andrea Cervesato
2026-10-14 11:39 ` Cyril Hrubis
2026-08-31 8:00 ` [LTP] [PATCH STAGING v4 10/16] fchroot07: test execve blocked by " Andrea Cervesato
2026-10-13 15:44 ` Cyril Hrubis
2026-08-31 8:00 ` [LTP] [PATCH STAGING v4 11/16] fchroot08: test failfs root fork inheritance Andrea Cervesato
2026-10-13 16:02 ` Cyril Hrubis
2026-08-31 8:00 ` [LTP] [PATCH STAGING v4 12/16] fchroot09: test setns escape from failfs root Andrea Cervesato
2026-10-14 11:52 ` Cyril Hrubis [this message]
2026-08-31 8:00 ` [LTP] [PATCH STAGING v4 13/16] fchroot10: test failfs entry without no_new_privs Andrea Cervesato
2026-10-14 12:11 ` Cyril Hrubis
2026-08-31 8:00 ` [LTP] [PATCH STAGING v4 14/16] fchroot11: test failfs entry with no_new_privs Andrea Cervesato
2026-10-14 14:20 ` Cyril Hrubis
2026-08-31 8:00 ` [LTP] [PATCH STAGING v4 15/16] fchroot12: test failfs entry with shared fs_struct Andrea Cervesato
2026-10-14 15:10 ` Cyril Hrubis
2026-08-31 8:00 ` [LTP] [PATCH STAGING v4 16/16] fchroot13: test failfs entry when chrooted Andrea Cervesato
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=as9s_vmNm66HStbG@yuki.lan \
--to=chrubis@suse.cz \
--cc=andrea.cervesato@suse.de \
--cc=ltp@lists.linux.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.