Linux kbuild/kconfig development
 help / color / mirror / Atom feed
From: "Gary Guo" <gary@garyguo.net>
To: "Ihor Solodrai" <ihor.solodrai@linux.dev>,
	"Alexei Starovoitov" <ast@kernel.org>,
	"Daniel Borkmann" <daniel@iogearbox.net>,
	"Andrii Nakryiko" <andrii@kernel.org>,
	"Martin KaFai Lau" <martin.lau@linux.dev>
Cc: "Gary Guo" <gary@garyguo.net>,
	"Thomas Weißschuh" <linux@weissschuh.net>,
	"Nathan Chancellor" <nathan@kernel.org>,
	"Nicolas Schier" <nsc@kernel.org>,
	bpf@vger.kernel.org, linux-kbuild@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v1] scripts/gen-btf.sh: Use CONFIG_SHELL for execution
Date: Wed, 21 Jan 2026 18:24:59 +0000	[thread overview]
Message-ID: <DFUH7UI3MM6F.1B30NTZ5NFSKR@garyguo.net> (raw)
In-Reply-To: <20260121181617.820300-1-ihor.solodrai@linux.dev>

On Wed Jan 21, 2026 at 6:16 PM GMT, Ihor Solodrai wrote:
> According to the docs [1], kernel build scripts should be executed via
> CONFIG_SHELL, which is sh by default.
>
> Fixup gen-btf.sh to be runnable with sh, and use CONFIG_SHELL at every
> invocation site.
>
> See relevant discussion for context [2].
>
> [1] https://docs.kernel.org/kbuild/makefiles.html#script-invocation
> [2] https://lore.kernel.org/bpf/CAADnVQ+dxmSNoJAGb6xV89ffUCKXe5CJXovXZt22nv5iYFV5mw@mail.gmail.com/
>
> Signed-off-by: Ihor Solodrai <ihor.solodrai@linux.dev>

I can indeed build again when applying this on top of linux-next. Thanks.

Tested-by: Gary Guo <gary@garyguo.net>

You probably also want to carry some Reported-by, Suggested-by and Fixes tags here.

Best,
Gary

> ---
>  scripts/Makefile.modfinal | 2 +-
>  scripts/gen-btf.sh        | 8 ++++----
>  scripts/link-vmlinux.sh   | 2 +-
>  3 files changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/scripts/Makefile.modfinal b/scripts/Makefile.modfinal
> index 422c56dc878e..adcbcde16a07 100644
> --- a/scripts/Makefile.modfinal
> +++ b/scripts/Makefile.modfinal
> @@ -43,7 +43,7 @@ quiet_cmd_btf_ko = BTF [M] $@
>  	if [ ! -f $(objtree)/vmlinux ]; then				\
>  		printf "Skipping BTF generation for %s due to unavailability of vmlinux\n" $@ 1>&2; \
>  	else	\
> -		$(srctree)/scripts/gen-btf.sh --btf_base $(objtree)/vmlinux $@; \
> +		$(CONFIG_SHELL) $(srctree)/scripts/gen-btf.sh --btf_base $(objtree)/vmlinux $@; \
>  	fi;
>  
>  # Same as newer-prereqs, but allows to exclude specified extra dependencies
> diff --git a/scripts/gen-btf.sh b/scripts/gen-btf.sh
> index be21ccee3487..8ca96eb10a69 100755
> --- a/scripts/gen-btf.sh
> +++ b/scripts/gen-btf.sh
> @@ -1,4 +1,4 @@
> -#!/bin/bash
> +#!/bin/sh
>  # SPDX-License-Identifier: GPL-2.0
>  # Copyright (c) 2025 Meta Platforms, Inc. and affiliates.
>  #
> @@ -81,7 +81,7 @@ gen_btf_data()
>  
>  gen_btf_o()
>  {
> -	local btf_data=${ELF_FILE}.btf.o
> +	btf_data=${ELF_FILE}.btf.o
>  
>  	# Create ${btf_data} which contains just .BTF section but no symbols. Add
>  	# SHF_ALLOC because .BTF will be part of the vmlinux image. --strip-all
> @@ -107,11 +107,11 @@ embed_btf_data()
>  	${OBJCOPY} --add-section .BTF=${ELF_FILE}.BTF ${ELF_FILE}
>  
>  	# a module might not have a .BTF_ids or .BTF.base section
> -	local btf_base="${ELF_FILE}.BTF.base"
> +	btf_base="${ELF_FILE}.BTF.base"
>  	if [ -f "${btf_base}" ]; then
>  		${OBJCOPY} --add-section .BTF.base=${btf_base} ${ELF_FILE}
>  	fi
> -	local btf_ids="${ELF_FILE}.BTF_ids"
> +	btf_ids="${ELF_FILE}.BTF_ids"
>  	if [ -f "${btf_ids}" ]; then
>  		${RESOLVE_BTFIDS} --patch_btfids ${btf_ids} ${ELF_FILE}
>  	fi
> diff --git a/scripts/link-vmlinux.sh b/scripts/link-vmlinux.sh
> index 08cd8e25c65c..16d6a048e07c 100755
> --- a/scripts/link-vmlinux.sh
> +++ b/scripts/link-vmlinux.sh
> @@ -206,7 +206,7 @@ fi
>  
>  if is_enabled CONFIG_DEBUG_INFO_BTF; then
>  	info BTF .tmp_vmlinux1
> -	if ! ${srctree}/scripts/gen-btf.sh .tmp_vmlinux1; then
> +	if ! ${CONFIG_SHELL} ${srctree}/scripts/gen-btf.sh .tmp_vmlinux1; then
>  		echo >&2 "Failed to generate BTF for vmlinux"
>  		echo >&2 "Try to disable CONFIG_DEBUG_INFO_BTF"
>  		exit 1


  reply	other threads:[~2026-01-21 18:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-21 18:16 [PATCH bpf-next v1] scripts/gen-btf.sh: Use CONFIG_SHELL for execution Ihor Solodrai
2026-01-21 18:24 ` Gary Guo [this message]
2026-01-21 18:30   ` Ihor Solodrai
2026-01-21 20:38     ` Alexei Starovoitov
2026-01-21 20:40 ` patchwork-bot+netdevbpf

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=DFUH7UI3MM6F.1B30NTZ5NFSKR@garyguo.net \
    --to=gary@garyguo.net \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=ihor.solodrai@linux.dev \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --cc=martin.lau@linux.dev \
    --cc=nathan@kernel.org \
    --cc=nsc@kernel.org \
    /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