From: linuxtestproject.agent@gmail.com
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] syscalls: add v7.3 syscall numbers
Date: Mon, 31 Aug 2026 09:06:33 +0000 [thread overview]
Message-ID: <20260831090633.9495-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260831-fchroot-v4-4-57cceb68f927@suse.com>
Hi Andrea,
On 31 Aug 2026, Andrea Cervesato wrote:
> syscalls: add v7.3 syscall numbers
--- [PATCH 4/16] ---
> +fchroot01 fchroot01
Medium: Linux 7.3 is stable, so this released syscall test belongs in the
regular syscall runtest file rather than the staging-only suite.
> +static struct tst_test test = {
> + .setup = setup,
> + .test_all = run,
> + .needs_root = 1,
> + .needs_tmpdir = 1,
> + .forks_child = 1,
> +};
Medium: Add `.min_kver = "7.3"`. On older kernels the direct syscall returns
ENOSYS and the test reports TFAIL instead of TCONF.
--- [PATCH 5/16] ---
> +fchroot02 fchroot02
Medium: Linux 7.3 is stable, so this entry belongs in the regular syscall
runtest file rather than the staging-only suite.
> +static struct tst_test test = {
> + .test = run,
> + .tcnt = ARRAY_SIZE(tcases),
> + .setup = setup,
> + .cleanup = cleanup,
> + .needs_tmpdir = 1,
> +};
Medium: Add `.min_kver = "7.3"` so older kernels skip instead of reporting
TFAIL when the syscall returns ENOSYS.
--- [PATCH 6/16] ---
> +fchroot03 fchroot03
Medium: Linux 7.3 is stable, so this entry belongs in the regular syscall
runtest file rather than the staging-only suite.
> +static struct tst_test test = {
> + .test = run,
> + .tcnt = ARRAY_SIZE(tcases),
> + .setup = setup,
> + .needs_root = 1,
> + .needs_tmpdir = 1,
> + .forks_child = 1,
> +};
Medium: Add `.min_kver = "7.3"` so older kernels skip instead of reporting
TFAIL when the syscall returns ENOSYS.
--- [PATCH 7/16] ---
> +fchroot04 fchroot04
Medium: Linux 7.3 is stable, so this entry belongs in the regular syscall
runtest file rather than the staging-only suite.
> +static struct tst_test test = {
> + .test_all = run,
> + .needs_root = 1,
> + .needs_tmpdir = 1,
> + .forks_child = 1,
> +};
Medium: Add `.min_kver = "7.3"` so older kernels skip instead of reporting
TFAIL when the syscall returns ENOSYS.
--- [PATCH 8/16] ---
> +fchroot05 fchroot05
Medium: Linux 7.3 is stable, so this entry belongs in the regular syscall
runtest file rather than the staging-only suite.
> +static struct tst_test test = {
> + .test_all = run,
> + .needs_root = 1,
> + .forks_child = 1,
> +};
Medium: Add `.min_kver = "7.3"` so older kernels skip instead of reporting
TFAIL when the syscall returns ENOSYS.
--- [PATCH 9/16] ---
> +fchroot06 fchroot06
Medium: Linux 7.3 is stable, so this entry belongs in the regular syscall
runtest file rather than the staging-only suite.
> +static struct tst_test test = {
> + .setup = setup,
> + .test_all = run,
> + .needs_root = 1,
> + .needs_tmpdir = 1,
> + .forks_child = 1,
> +};
Medium: Add `.min_kver = "7.3"` so older kernels skip instead of reporting
TFAIL when the syscall returns ENOSYS.
--- [PATCH 10/16] ---
> +fchroot07 fchroot07
Medium: Linux 7.3 is stable, so this entry belongs in the regular syscall
runtest file rather than the staging-only suite.
> +static struct tst_test test = {
> + .setup = setup,
> + .test_all = run,
> + .needs_root = 1,
> + .forks_child = 1,
> + .child_needs_reinit = 1,
> +};
Medium: Add `.min_kver = "7.3"` so older kernels skip instead of reporting
TFAIL when the syscall returns ENOSYS.
--- [PATCH 11/16] ---
> +fchroot08 fchroot08
Medium: Linux 7.3 is stable, so this entry belongs in the regular syscall
runtest file rather than the staging-only suite.
> +static struct tst_test test = {
> + .test_all = run,
> + .setup = setup,
> + .needs_root = 1,
> + .forks_child = 1,
> + .needs_tmpdir = 1,
> +};
Medium: Add `.min_kver = "7.3"` so older kernels skip instead of reporting
TFAIL when the syscall returns ENOSYS.
--- [PATCH 12/16] ---
> +fchroot09 fchroot09
Medium: Linux 7.3 is stable, so this entry belongs in the regular syscall
runtest file rather than the staging-only suite.
> + * 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
Low: A pre-opened directory fd also permits a privileged process to escape
with `fchroot()`, or with `fchdir()` followed by `chroot(".")`. Describe
`setns()` as one escape mechanism rather than the remaining one.
> +static struct tst_test test = {
> + .test_all = run,
> + .setup = setup,
> + .needs_root = 1,
> + .forks_child = 1,
> + .needs_tmpdir = 1,
> +};
Medium: Add `.min_kver = "7.3"` so older kernels skip instead of reporting
TFAIL when the syscall returns ENOSYS.
--- [PATCH 13/16] ---
> +fchroot10 fchroot10
Medium: Linux 7.3 is stable, so this entry belongs in the regular syscall
runtest file rather than the staging-only suite.
> +static struct tst_test test = {
> + .setup = setup,
> + .test_all = run,
> + .needs_root = 1,
> + .forks_child = 1,
> +};
Medium: Add `.min_kver = "7.3"` so older kernels skip instead of reporting
TFAIL when the syscall returns ENOSYS.
--- [PATCH 14/16] ---
> +fchroot11 fchroot11
Medium: Linux 7.3 is stable, so this entry belongs in the regular syscall
runtest file rather than the staging-only suite.
> + TST_EXP_FAIL(unshare(CLONE_NEWUSER), EPERM,
> + "user namespace creation blocked by the failfs root");
Medium: EPERM can also come from `security_create_user_ns()` or a policy that
disables unprivileged user namespaces, producing a false pass. First verify
in a separate child, before entering failfs, that this user can create a user
namespace; skip if it cannot.
> +static struct tst_test test = {
> + .setup = setup,
> + .test_all = run,
> + .needs_root = 1,
> + .forks_child = 1,
> + .needs_kconfigs = (const char *[]) {
> + "CONFIG_USER_NS=y",
> + NULL,
> + }
> +};
Medium: Add `.min_kver = "7.3"` so older kernels skip instead of reporting
TFAIL when the syscall returns ENOSYS.
--- [PATCH 15/16] ---
> +fchroot12 fchroot12
Medium: Linux 7.3 is stable, so this entry belongs in the regular syscall
runtest file rather than the staging-only suite.
> +static struct tst_test test = {
> + .setup = setup,
> + .test_all = run,
> + .needs_root = 1,
> + .forks_child = 1,
> +};
Medium: Add `.min_kver = "7.3"` so older kernels skip instead of reporting
TFAIL when the syscall returns ENOSYS.
--- [PATCH 16/16] ---
> +fchroot13 fchroot13
Medium: Linux 7.3 is stable, so this entry belongs in the regular syscall
runtest file rather than the staging-only suite.
> +static struct tst_test test = {
> + .setup = setup,
> + .test_all = run,
> + .needs_root = 1,
> + .needs_tmpdir = 1,
> + .forks_child = 1,
> +};
Medium: Add `.min_kver = "7.3"` so older kernels skip instead of reporting
TFAIL when the syscall returns ENOSYS.
Verdict - Needs revision
---
Note:
The agent can sometimes produce false positives although often its
findings are genuine. If you find issues with the review, please
comment this email or ignore the suggestions.
Regards,
LTP AI Reviewer
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-08-31 9:06 UTC|newest]
Thread overview: 23+ 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 ` linuxtestproject.agent [this message]
2026-08-31 8:00 ` [LTP] [PATCH STAGING v4 05/16] fchroot02: test fchroot() invalid arguments Andrea Cervesato
2026-08-31 8:00 ` [LTP] [PATCH STAGING v4 06/16] fchroot03: test fchroot() permission checks Andrea Cervesato
2026-08-31 8:00 ` [LTP] [PATCH STAGING v4 07/16] fchroot04: test fchroot() into failfs as root Andrea Cervesato
2026-08-31 8:00 ` [LTP] [PATCH STAGING v4 08/16] fchroot05: test failfs root can not be referenced Andrea Cervesato
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-08-31 8:00 ` [LTP] [PATCH STAGING v4 11/16] fchroot08: test failfs root fork inheritance Andrea Cervesato
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
-- strict thread matches above, loose matches on Subject: below --
2026-08-28 14:11 [LTP] [PATCH v3 02/15] syscalls: update outdated syscall entries Andrea Cervesato
2026-08-28 21:14 ` [LTP] syscalls: add v7.3 syscall numbers linuxtestproject.agent
2026-08-20 7:44 [LTP] [PATCH v2 01/16] " Andrea Cervesato
2026-08-20 8:34 ` [LTP] " linuxtestproject.agent
2026-08-20 8:37 ` Andrea Cervesato via ltp
2026-08-19 21:24 [LTP] [PATCH 03/16] lapi: fallback fchroot() parameters Andrea Cervesato
2026-08-19 22:27 ` [LTP] syscalls: add v7.3 syscall numbers linuxtestproject.agent
2026-08-20 6:03 ` Andrea Cervesato via ltp
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=20260831090633.9495-1-linuxtestproject.agent@gmail.com \
--to=linuxtestproject.agent@gmail.com \
--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