From: patchwork-bot+netdevbpf@kernel.org
To: None <qmo@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@google.com, haoluo@google.com,
jolsa@kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next v2] libbpf: Prevent null-pointer dereference when prog to load has no BTF
Date: Thu, 14 Mar 2024 20:50:30 +0000 [thread overview]
Message-ID: <171044943046.22144.10648250930242367803.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240314150438.232462-1-qmo@kernel.org>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Thu, 14 Mar 2024 15:04:38 +0000 you wrote:
> From: Quentin Monnet <qmo@kernel.org>
>
> In bpf_objec_load_prog(), there's no guarantee that obj->btf is non-NULL
> when passing it to btf__fd(), and this function does not perform any
> check before dereferencing its argument (as bpf_object__btf_fd() used to
> do). As a consequence, we get segmentation fault errors in bpftool (for
> example) when trying to load programs that come without BTF information.
>
> [...]
Here is the summary with links:
- [bpf-next,v2] libbpf: Prevent null-pointer dereference when prog to load has no BTF
https://git.kernel.org/bpf/bpf-next/c/9bf48fa19a4b
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:[~2024-03-14 20:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 15:04 [PATCH bpf-next v2] libbpf: Prevent null-pointer dereference when prog to load has no BTF qmo
2024-03-14 20: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=171044943046.22144.10648250930242367803.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=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=qmo@kernel.org \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yonghong.song@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.