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 11/16] fchroot08: test failfs root fork inheritance
Date: Tue, 13 Oct 2026 18:02:12 +0200 [thread overview]
Message-ID: <as5WBKmXm22S6PrQ@yuki.lan> (raw)
In-Reply-To: <20260831-fchroot-v4-11-57cceb68f927@suse.com>
Hi!
> Verify that the root moved into failfs by fchroot() lives in the
> fs_struct which is duplicated on fork, so a child of a process with
> the failfs root also fails every absolute path lookup with
> EOPNOTSUPP.
>
> Signed-off-by: Andrea Cervesato <andrea.cervesato@suse.com>
> ---
> runtest/staging | 1 +
> testcases/kernel/syscalls/fchroot/.gitignore | 1 +
> testcases/kernel/syscalls/fchroot/fchroot08.c | 69 +++++++++++++++++++++++++++
> 3 files changed, 71 insertions(+)
>
> diff --git a/runtest/staging b/runtest/staging
> index b8954bb5a..8dfe95c4a 100644
> --- a/runtest/staging
> +++ b/runtest/staging
> @@ -7,3 +7,4 @@ fchroot04 fchroot04
> fchroot05 fchroot05
> fchroot06 fchroot06
> fchroot07 fchroot07
> +fchroot08 fchroot08
> diff --git a/testcases/kernel/syscalls/fchroot/.gitignore b/testcases/kernel/syscalls/fchroot/.gitignore
> index bfa2a8ce1..0a2510d8a 100644
> --- a/testcases/kernel/syscalls/fchroot/.gitignore
> +++ b/testcases/kernel/syscalls/fchroot/.gitignore
> @@ -6,3 +6,4 @@ fchroot05
> fchroot06
> fchroot07
> fchroot07_child
> +fchroot08
> diff --git a/testcases/kernel/syscalls/fchroot/fchroot08.c b/testcases/kernel/syscalls/fchroot/fchroot08.c
> new file mode 100644
> index 000000000..3180191e7
> --- /dev/null
> +++ b/testcases/kernel/syscalls/fchroot/fchroot08.c
> @@ -0,0 +1,69 @@
> +// SPDX-License-Identifier: GPL-2.0-or-later
> +/*
> + * Copyright (C) 2026 SUSE LLC Andrea Cervesato <andrea.cervesato@suse.com>
> + */
> +
> +/*\
> + * Test that the failfs root is inherited across :manpage:`fork(2)`.
> + *
> + * The root moved into failfs by :manpage:`fchroot(2)` lives in the
> + * fs_struct which is duplicated on :manpage:`fork(2)`, so a child of a process with the
> + * failfs root also fails every absolute path lookup with ``EOPNOTSUPP``.
> + *
> + * Root is required because entering failfs with the ``FD_FAILFS_ROOT``
> + * sentinel requires ``CAP_SYS_CHROOT``.
> + *
> + * 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/wait.h>
> +#include "tst_test.h"
> +#include "lapi/fcntl.h"
> +#include "lapi/syscalls.h"
> +
> +#define ABSDIR "abs"
> +
> +static void run(void)
> +{
> + if (SAFE_FORK())
> + return;
> +
> + pid_t pid;
> +
> + TST_EXP_PASS(tst_syscall(__NR_fchroot, FD_FAILFS_ROOT, 0),
> + "fchroot() with the FD_FAILFS_ROOT sentinel");
> +
> + pid = SAFE_FORK();
> + if (!pid) {
> + TST_EXP_FAIL2(open(ABSDIR, O_PATH), EOPNOTSUPP,
> + "absolute lookup in a forked child");
> + exit(0);
> + }
> +
> + SAFE_WAITPID(pid, NULL, 0);
> +
> + exit(0);
> +}
> +
> +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);
I do not understand why we do the symlink here?
Why don't we pass the abs_path to the syscall directly?
> +}
> +
> +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-13 16:02 UTC|newest]
Thread overview: 25+ 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-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 [this message]
2026-08-31 8:00 ` [LTP] [PATCH STAGING v4 12/16] fchroot09: test setns escape from failfs root Andrea Cervesato
2026-08-31 8:00 ` [LTP] [PATCH STAGING v4 13/16] fchroot10: test failfs entry without no_new_privs Andrea Cervesato
2026-08-31 8:00 ` [LTP] [PATCH STAGING v4 14/16] fchroot11: test failfs entry with no_new_privs Andrea Cervesato
2026-08-31 8:00 ` [LTP] [PATCH STAGING v4 15/16] fchroot12: test failfs entry with shared fs_struct Andrea Cervesato
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=as5WBKmXm22S6PrQ@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox