From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
martin.lau@kernel.org, kernel-team@meta.com
Subject: Re: [PATCH bpf-next] libbpf: fix hypothetical STT_SECTION extern NULL deref case
Date: Fri, 21 Feb 2025 02:50:37 +0000 [thread overview]
Message-ID: <174010623724.1561130.4152072107672496366.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250220002821.834400-1-andrii@kernel.org>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 19 Feb 2025 16:28:21 -0800 you wrote:
> Fix theoretical NULL dereference in linker when resolving *extern*
> STT_SECTION symbol against not-yet-existing ELF section. Not sure if
> it's possible in practice for valid ELF object files (this would require
> embedded assembly manipulations, at which point BTF will be missing),
> but fix the s/dst_sym/dst_sec/ typo guarding this condition anyways.
>
> Fixes: faf6ed321cf6 ("libbpf: Add BPF static linker APIs")
> Fixes: a46349227cd8 ("libbpf: Add linker extern resolution support for functions and global variables")
> Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
>
> [...]
Here is the summary with links:
- [bpf-next] libbpf: fix hypothetical STT_SECTION extern NULL deref case
https://git.kernel.org/bpf/bpf-next/c/e0525cd72b59
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-02-21 2:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 0:28 [PATCH bpf-next] libbpf: fix hypothetical STT_SECTION extern NULL deref case Andrii Nakryiko
2025-02-21 2:50 ` 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=174010623724.1561130.4152072107672496366.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=kernel-team@meta.com \
--cc=martin.lau@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