All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "André Almeida" <andrealmeid@igalia.com>
Cc: linux-s390@vger.kernel.org, "Vasily Gorbik" <gor@linux.ibm.com>,
	"Alexander Gordeev" <agordeev@linux.ibm.com>,
	"Christian Borntraeger" <borntraeger@linux.ibm.vom>,
	"Heiko Carstens" <hca@linux.ibm.com>
Subject: Re: [PATCH v5 07/13] mips: Remove duplicated syscallnr.sh
Date: Wed, 12 Aug 2026 17:48:02 +0000	[thread overview]
Message-ID: <20260812174803.75A331F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260812-tonyk-syscall_table-v5-7-3d383927c609@igalia.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The MIPS kernel build fails because an empty, unquoted Make variable causes `scripts/syscallnr.sh` to misparse its arguments.
--

--- Patch [7]: [PATCH v5 07/13] mips: Remove duplicated syscallnr.sh ---
commit 877d5f006e4ab42c99a338fbffa9cb65343bea2e
Author: André Almeida <andrealmeid@igalia.com>

mips: Remove duplicated syscallnr.sh

This commit removes the MIPS-specific syscallnr.sh script and switches to
using the common script in scripts/syscallnr.sh for generating syscall numbers.

> diff --git a/arch/mips/kernel/syscalls/Makefile b/arch/mips/kernel/syscalls/Makefile
> index 56f6f093bb88e..69adc21483edf 100644
> --- a/arch/mips/kernel/syscalls/Makefile
> +++ b/arch/mips/kernel/syscalls/Makefile
> @@ -5,16 +5,17 @@ uapi := arch/$(SRCARCH)/include/generated/uapi/asm
>  $(shell mkdir -p $(uapi) $(kapi))
>  
>  syshdr := $(srctree)/scripts/syscallhdr.sh
> -sysnr := $(src)/syscallnr.sh
> +sysnr := $(srctree)/scripts/syscallnr.sh
>  systbl := $(srctree)/scripts/syscalltbl.sh
>  
>  quiet_cmd_syshdr = SYSHDR  $@
>        cmd_syshdr = $(CONFIG_SHELL) $(syshdr) --offset __NR_Linux $< $@
>  
>  quiet_cmd_sysnr = SYSNR   $@
> -      cmd_sysnr = $(CONFIG_SHELL) '$(sysnr)' '$<' '$@'		\
> -		  '$(sysnr_abis_$(basetarget))'			\
> -		  '$(sysnr_pfx_$(basetarget))'
> +      cmd_sysnr = $(CONFIG_SHELL) $(sysnr) \
> +		  --prefix $(sysnr_pfx_$(basetarget))_Linux_ \
> +		  --abis $(sysnr_abis_$(basetarget)) \

[Severity: Low]
Does this break the build when $(sysnr_abis_$(basetarget)) evaluates to an
empty string?

Because $(sysnr_abis_$(basetarget)) is unquoted, if it is empty, the shell
command becomes:

  --abis $< $@

This causes scripts/syscallnr.sh to consume the input file $< as the argument
to --abis, leaving only the output file $@ as a positional argument. Since the
script expects exactly two positional arguments, the script's parameter count
check would fail and terminate with a usage error.

> +		  $< $@
>  
>  quiet_cmd_systbl = SYSTBL  $@
>        cmd_systbl = $(CONFIG_SHELL) $(systbl) $< $@

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260812-tonyk-syscall_table-v5-0-3d383927c609@igalia.com?part=7

  reply	other threads:[~2026-08-12 17:48 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 [this message]
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
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=20260812174803.75A331F000E9@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 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.