From: sashiko-bot@kernel.org
To: "André Almeida" <andrealmeid@igalia.com>
Cc: linux-s390@vger.kernel.org,
"Alexander Gordeev" <agordeev@linux.ibm.com>,
"Christian Borntraeger" <borntraeger@linux.ibm.com>,
"Vasily Gorbik" <gor@linux.ibm.com>,
"Heiko Carstens" <hca@linux.ibm.com>
Subject: Re: [PATCH v8 03/12] scripts/syscall.tbl: Use the common table
Date: Sat, 19 Sep 2026 00:41:20 +0000 [thread overview]
Message-ID: <20260919004121.37C761F00898@smtp.kernel.org> (raw)
In-Reply-To: <20260918-tonyk-syscall_table-v8-3-0e2d60cad13e@igalia.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Critical] arm64: compat: ABI breakage due to omitted clone3 syscall
- [Medium] perf: silent trace breakage on RISC-V/CSKY when syncing syscall.tbl
--
commit 6f36ef0832663a9b88501de9d0a2dada0399dd37
Author: André Almeida <andrealmeid@igalia.com>
scripts/syscall.tbl: Use the common table
This patch removes duplicated syscalls from architecture-specific tables by
moving them to a common table. It creates a new scripts/syscall_common.tbl
and adjusts build scripts and Makefiles to use it.
> diff --git a/arch/arm64/kernel/Makefile.syscalls b/arch/arm64/kernel/Makefile.syscalls
> --- a/arch/arm64/kernel/Makefile.syscalls
> +++ b/arch/arm64/kernel/Makefile.syscalls
> @@ -1,6 +1,6 @@
> # SPDX-License-Identifier: GPL-2.0
>
> syscall_abis_32 +=
> -syscall_abis_64 += renameat rlimit memfd_secret
> +syscall_abis_64 += renameat rlimit memfd_secret clone3
[Severity: Critical]
Does this code omit clone3 for 32-bit AArch32 compat processes?
The new scripts/syscall_common.tbl defines clone3 under the explicit ABI
name clone3 instead of common. Because syscall_abis_32 does not include
clone3 here, the build system will not generate the clone3 entry for the
32-bit compat table.
Consequently, 32-bit AArch32 binaries running on arm64 that invoke clone3
will receive -ENOSYS since the generated system call table will populate
the slot with sys_ni_syscall.
[ ... ]
> diff --git a/scripts/syscall.tbl b/scripts/syscall.tbl
> --- a/scripts/syscall.tbl
> +++ b/scripts/syscall.tbl
> @@ -344,72 +344,3 @@
> 293 common rseq sys_rseq
> 294 common kexec_file_load sys_kexec_file_load
> # 295 through 402 are unassigned to sync up with generic numbers don't use
> -403 32 clock_gettime64 sys_clock_gettime
[Severity: Medium]
Will moving these syscalls out of scripts/syscall.tbl break perf trace
for generic architectures like RISC-V and CSKY?
The tooling script tools/perf/trace/beauty/syscalltbl.sh hardcodes reading
the main syscall.tbl when building tables for generic architectures:
tools/perf/trace/beauty/syscalltbl.sh:build_tables() {
...
build_tables "$tools_dir/scripts/syscall.tbl" "$outfile" ...
...
}
Because it completely ignores the new scripts/syscall_common.tbl, when a
developer later syncs the modified scripts/syscall.tbl into the tools/
directory to resolve check-headers.sh build warnings, perf trace will silently
lose the capability to map IDs to names for all of these removed syscalls.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260918-tonyk-syscall_table-v8-0-0e2d60cad13e@igalia.com?part=3
next prev parent reply other threads:[~2026-09-19 0:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 0:31 [PATCH v8 00/12] syscalls: Add a shared table for all archs André Almeida
2026-09-19 0:31 ` [PATCH v8 01/12] syscalls: Make --abis parsing more robust André Almeida
2026-09-19 0:41 ` sashiko-bot
2026-09-19 0:31 ` [PATCH v8 02/12] syscalls: Create unified partial table for all archs André Almeida
2026-09-19 0:41 ` sashiko-bot
2026-09-19 0:31 ` [PATCH v8 03/12] scripts/syscall.tbl: Use the common table André Almeida
2026-09-19 0:41 ` sashiko-bot [this message]
2026-09-19 0:31 ` [PATCH v8 04/12] s390: Use the common syscall table André Almeida
2026-09-19 0:50 ` sashiko-bot
2026-09-19 0:31 ` [PATCH v8 05/12] sparc: " André Almeida
2026-09-19 0:45 ` sashiko-bot
2026-09-19 0:31 ` [PATCH v8 06/12] mips: Remove duplicated syscallnr.sh André Almeida
2026-09-19 0:45 ` sashiko-bot
2026-09-19 0:31 ` [PATCH v8 07/12] mips: Get rid of custom mips ABIs for syscall tables André Almeida
2026-09-19 0:52 ` sashiko-bot
2026-09-19 0:31 ` [PATCH v8 08/12] mips: Use the common syscall table André Almeida
2026-09-19 0:54 ` sashiko-bot
2026-09-19 0:31 ` [PATCH v8 09/12] syscalls: Add an option for offsetting the common table André Almeida
2026-09-19 0:55 ` sashiko-bot
2026-09-19 0:31 ` [PATCH v8 10/12] alpha: Define entry point for set_mempolicy_home_node syscall André Almeida
2026-09-19 0:55 ` sashiko-bot
2026-09-19 0:31 ` [PATCH v8 11/12] alpha: Remove alpha_ prefix from custom syscall entries André Almeida
2026-09-19 0:59 ` sashiko-bot
2026-09-19 0:31 ` [PATCH v8 12/12] alpha: Use the common syscall table André Almeida
2026-09-19 1:01 ` sashiko-bot
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=20260919004121.37C761F00898@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=andrealmeid@igalia.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.