BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ihor Solodrai <ihor.solodrai@linux.dev>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	martin.lau@linux.dev, eddyz87@gmail.com, nathan@kernel.org,
	nsc@kernel.org, bpf@vger.kernel.org,
	linux-kbuild@vger.kernel.org
Subject: Re: [PATCH bpf-next v2] resolve_btfids: Implement --patch_btfids
Date: Wed, 31 Dec 2025 17:10:11 +0000	[thread overview]
Message-ID: <176720101127.3562703.15519413804763442905.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251231012558.1699758-1-ihor.solodrai@linux.dev>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Tue, 30 Dec 2025 17:25:57 -0800 you wrote:
> Recent changes in BTF generation [1] rely on ${OBJCOPY} command to
> update .BTF_ids section data in target ELF files.
> 
> This exposed a bug in llvm-objcopy --update-section code path, that
> may lead to corruption of a target ELF file. Specifically, because of
> the bug st_shndx of some symbols may be (incorrectly) set to 0xffff
> (SHN_XINDEX) [2][3].
> 
> [...]

Here is the summary with links:
  - [bpf-next,v2] resolve_btfids: Implement --patch_btfids
    https://git.kernel.org/bpf/bpf-next/c/1a8fa7faf489

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-12-31 17:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-31  1:25 [PATCH bpf-next v2] resolve_btfids: Implement --patch_btfids Ihor Solodrai
2025-12-31 17:07 ` Alexei Starovoitov
2025-12-31 17:10 ` patchwork-bot+netdevbpf [this message]

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=176720101127.3562703.15519413804763442905.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=ihor.solodrai@linux.dev \
    --cc=linux-kbuild@vger.kernel.org \
    --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