From: patchwork-bot+netdevbpf@kernel.org
To: Tengda Wu <wutengda@huaweicloud.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
john.fastabend@gmail.com, andrii@kernel.org,
martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, jolsa@kernel.org, hffilwlqm@gmail.com
Subject: Re: [PATCH bpf v4 0/2] bpf: Fix null-pointer-deref in resolve_prog_type()
Date: Fri, 12 Jul 2024 20:20:32 +0000 [thread overview]
Message-ID: <172081563215.23700.10781296355063378646.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240711145819.254178-1-wutengda@huaweicloud.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Thu, 11 Jul 2024 22:58:17 +0800 you wrote:
> Hi,
>
> This patchset is going to fix null-pointer-deref in resolve_prog_type()
> for BPF_PROG_TYPE_EXT.
>
> `prog->aux->dst_prog` in resolve_prog_type() is assigned by
> `attach_prog_fd`, and would be NULL if `attach_prog_fd` is not
> provided. Loading EXT prog with bpf_dynptr_from_skb() kfunc call
> in this way will lead to null-pointer-deref.
>
> [...]
Here is the summary with links:
- [bpf,v4,1/2] bpf: Fix null pointer dereference in resolve_prog_type() for BPF_PROG_TYPE_EXT
https://git.kernel.org/bpf/bpf-next/c/f7866c358733
- [bpf,v4,2/2] selftests/bpf: Test for null-pointer-deref bugfix in resolve_prog_type()
https://git.kernel.org/bpf/bpf-next/c/e435b043d89a
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-07-12 20:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 14:58 [PATCH bpf v4 0/2] bpf: Fix null-pointer-deref in resolve_prog_type() Tengda Wu
2024-07-11 14:58 ` [PATCH bpf v4 1/2] bpf: Fix null pointer dereference in resolve_prog_type() for BPF_PROG_TYPE_EXT Tengda Wu
2024-07-23 14:13 ` Leon Hwang
2024-07-11 14:58 ` [PATCH bpf v4 2/2] selftests/bpf: Test for null-pointer-deref bugfix in resolve_prog_type() Tengda Wu
2024-07-12 20:20 ` 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=172081563215.23700.10781296355063378646.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=hffilwlqm@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=wutengda@huaweicloud.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox