From: sashiko-bot@kernel.org
To: "André Almeida" <andrealmeid@igalia.com>
Cc: "Alexander Gordeev" <agordeev@linux.ibm.com>,
"Vasily Gorbik" <gor@linux.ibm.com>,
linux-s390@vger.kernel.org,
"Christian Borntraeger" <borntraeger@linux.ibm.vom>,
"Heiko Carstens" <hca@linux.ibm.com>
Subject: Re: [PATCH v5 09/13] mips: Use the common syscall table
Date: Wed, 12 Aug 2026 17:53:38 +0000 [thread overview]
Message-ID: <20260812175338.AB9D11F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260812-tonyk-syscall_table-v5-9-3d383927c609@igalia.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Build failure for MIPS N32 and N64 ABIs due to missing prerequisites and incorrect script arguments in Makefile, as well as broken incremental builds.
--
--- Patch [9]: [PATCH v5 09/13] mips: Use the common syscall table ---
commit 42dc635e6909962793a0c1f2315995398f780f3d
Author: André Almeida <andrealmeid@igalia.com>
mips: Use the common syscall table
This commit merges the n32 and n64 syscall tables into a single table and
updates the toolchain to use this common table. It also drops duplicated
code and modifies the MIPS build Makefile to adapt to these changes.
> diff --git a/arch/mips/kernel/syscalls/Makefile b/arch/mips/kernel/syscalls/Makefile
> index 1bfc2346d1009..f6a41ee9e38ad 100644
> --- a/arch/mips/kernel/syscalls/Makefile
> +++ b/arch/mips/kernel/syscalls/Makefile
> @@ -7,16 +7,21 @@ $(shell mkdir -p $(uapi) $(kapi))
> syshdr := $(srctree)/scripts/syscallhdr.sh
> sysnr := $(srctree)/scripts/syscallnr.sh
> systbl := $(srctree)/scripts/syscalltbl.sh
> +systbl_common := $(srctree)/scripts/syscall_common.tbl
>
> quiet_cmd_syshdr = SYSHDR $@
> - cmd_syshdr = $(CONFIG_SHELL) $(syshdr) --offset __NR_Linux $< $@
> + cmd_syshdr = $(CONFIG_SHELL) $(syshdr) --offset __NR_Linux \
> + --common-tbl $(systbl_common) \
> + --abis $(abis_$*) $< $@
[Severity: Low]
Does this cause the build script to fail for n32 and n64? The cmd_syshdr
command still references $<. In the $(uapi)/unistd_%.h rule below, this
evaluates to $(src)/syscall_%.tbl, which no longer exists for those ABIs.
> quiet_cmd_sysnr = SYSNR $@
> cmd_sysnr = $(CONFIG_SHELL) $(sysnr) \
> --prefix $(sysnr_pfx_$(basetarget))_Linux_ $< $@
>
> quiet_cmd_systbl = SYSTBL $@
> - cmd_systbl = $(CONFIG_SHELL) $(systbl) $< $@
> + cmd_systbl = $(CONFIG_SHELL) $(systbl) \
> + --common-tbl $(systbl_common) \
> + --abis $(abis_$*) $(src_$*) $@
>
> $(uapi)/unistd_%.h: $(src)/syscall_%.tbl $(syshdr) FORCE
> $(call if_changed,syshdr)
[Severity: Low]
Will this rule break since it still relies on $(src)/syscall_%.tbl? Since
syscall_n32.tbl and syscall_n64.tbl were deleted, this might cause make
to fail when attempting to build the uapi headers.
> @@ -25,10 +30,20 @@ sysnr_pfx_unistd_nr_n32 := N32
> sysnr_pfx_unistd_nr_n64 := 64
> sysnr_pfx_unistd_nr_o32 := O32
>
> -$(kapi)/unistd_nr_%.h: $(src)/syscall_%.tbl $(sysnr) FORCE
> +abis := common,__clone3
> +
> +abis_n32 := $(abis),32
> +abis_o32 := $(abis),32
> +abis_n64 := $(abis),64
> +
> +src_n32 := $(src)/syscall_n.tbl
> +src_n64 := $(src)/syscall_n.tbl
> +src_o32 := $(src)/syscall_o32.tbl
> +
> +$(kapi)/unistd_nr_%.h: $(systbl_common) $(sysnr) FORCE
> $(call if_changed,sysnr)
>
> -$(kapi)/syscall_table_%.h: $(src)/syscall_%.tbl $(systbl) FORCE
> +$(kapi)/syscall_table_%.h: $(systbl) FORCE
> $(call if_changed,systbl)
[Severity: Low]
Can removing the $(src)/syscall_%.tbl dependency break incremental builds?
It appears that if the source table is modified, this rule will no longer
trigger a rebuild of the syscall_table_%.h header.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260812-tonyk-syscall_table-v5-0-3d383927c609@igalia.com?part=9
next prev parent reply other threads:[~2026-08-12 17:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 17:38 [PATCH v5 00/13] syscalls: Add a shared table for all archs André Almeida
2026-08-12 17:38 ` [PATCH v5 01/13] syscalls: Make --abis parsing more robust André Almeida
2026-08-12 17:50 ` sashiko-bot
2026-08-12 17:38 ` [PATCH v5 02/13] syscalls: Create unified partial table for all archs André Almeida
2026-08-12 17:49 ` sashiko-bot
2026-08-12 17:38 ` [PATCH v5 03/13] scripts/syscall.tbl: Use the common table André Almeida
2026-08-12 17:53 ` sashiko-bot
2026-08-12 17:38 ` [PATCH v5 04/13] arm: Use the common syscall table André Almeida
2026-08-12 18:10 ` sashiko-bot
2026-08-12 17:38 ` [PATCH v5 05/13] s390: " André Almeida
2026-08-12 17:50 ` sashiko-bot
2026-08-12 17:38 ` [PATCH v5 06/13] sparc: " André Almeida
2026-08-12 17:48 ` sashiko-bot
2026-08-12 17:38 ` [PATCH v5 07/13] mips: Remove duplicated syscallnr.sh André Almeida
2026-08-12 17:48 ` sashiko-bot
2026-08-12 17:38 ` [PATCH v5 08/13] mips: Get rid of custom mips ABIs for syscall tables André Almeida
2026-08-12 17:49 ` sashiko-bot
2026-08-12 17:38 ` [PATCH v5 09/13] mips: Use the common syscall table André Almeida
2026-08-12 17:53 ` sashiko-bot [this message]
2026-08-12 17:38 ` [PATCH v5 10/13] syscalls: Add an option for offsetting the common table André Almeida
2026-08-12 17:56 ` sashiko-bot
2026-08-12 17:38 ` [PATCH v5 11/13] alpha: Define entry point for set_mempolicy_home_node syscall André Almeida
2026-08-12 17:57 ` sashiko-bot
2026-08-12 17:38 ` [PATCH v5 12/13] alpha: Remove alpha_ prefix from custom syscall entries André Almeida
2026-08-12 17:58 ` sashiko-bot
2026-08-12 17:38 ` [PATCH v5 13/13] alpha: Use the common syscall table André Almeida
2026-08-12 18: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=20260812175338.AB9D11F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=andrealmeid@igalia.com \
--cc=borntraeger@linux.ibm.vom \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox