public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: Nicolas Schier <nsc@kernel.org>,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
	bpf@vger.kernel.org
Subject: Re: [PATCH] kbuild: install-extmod-build: Package resolve_btfids if necessary
Date: Thu, 26 Feb 2026 13:37:58 -0700	[thread overview]
Message-ID: <20260226203758.GC3196155@ax162> (raw)
In-Reply-To: <20260226-kbuild-resolve_btfids-v1-1-2bf38b93dfe7@linutronix.de>

On Thu, Feb 26, 2026 at 08:41:48AM +0100, Thomas Weißschuh wrote:
> When CONFIG_DEBUG_INFO_BTF_MODULES is enabled and vmlinux is available,
> Makefilefile.modfinal and gen-btf.sh will try to use resolve_btfids
> on the module .ko. install-extmod-build currently does not package
> resolve_btfids, so that step fails.

Heh, ironic that I was just looking in that area yesterday and I had
thought that this would be necessary if vmlinux is available but then
never followed up... Thanks for this.

> Also package resolve_btfids if it may get used.
> 
> Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>

Nicolas, can I take this as a fix?

> ---
>  scripts/package/install-extmod-build | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/scripts/package/install-extmod-build b/scripts/package/install-extmod-build
> index 2576cf7902db..f12e1ffe409e 100755
> --- a/scripts/package/install-extmod-build
> +++ b/scripts/package/install-extmod-build
> @@ -32,6 +32,10 @@ mkdir -p "${destdir}"
>  		echo tools/objtool/objtool
>  	fi
>  
> +	if is_enabled CONFIG_DEBUG_INFO_BTF_MODULES; then
> +		echo tools/bpf/resolve_btfids/resolve_btfids
> +	fi
> +
>  	echo Module.symvers
>  	echo "arch/${SRCARCH}/include/generated"
>  	echo include/config/auto.conf
> 
> ---
> base-commit: 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f
> change-id: 20260226-kbuild-resolve_btfids-ca233983ebbb
> 
> Best regards,
> -- 
> Thomas Weißschuh <thomas.weissschuh@linutronix.de>
> 

  reply	other threads:[~2026-02-26 20:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-26  7:41 [PATCH] kbuild: install-extmod-build: Package resolve_btfids if necessary Thomas Weißschuh
2026-02-26 20:37 ` Nathan Chancellor [this message]
2026-02-26 20:47   ` Nicolas Schier
2026-03-05  0:36 ` Nathan Chancellor

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=20260226203758.GC3196155@ax162 \
    --to=nathan@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nsc@kernel.org \
    --cc=thomas.weissschuh@linutronix.de \
    /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