From: patchwork-bot+netdevbpf@kernel.org
To: Eduard Zingerman <eddyz87@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, martin.lau@linux.dev, kernel-team@fb.com,
yonghong.song@linux.dev, mejedi@gmail.com, lkp@intel.com,
dan.carpenter@linaro.org
Subject: Re: [PATCH bpf 1/2] bpf: fix NPE when computing changes_pkt_data of program w/o subprograms
Date: Thu, 12 Dec 2024 19:50:31 +0000 [thread overview]
Message-ID: <173403303164.2422426.1574242566292619873.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241212070711.427443-1-eddyz87@gmail.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 11 Dec 2024 23:07:10 -0800 you wrote:
> bpf_prog_aux->func field might be NULL if program does not have
> subprograms except for main sub-program. The fixed commit does
> bpf_prog_aux->func access unconditionally, which might lead to null
> pointer dereference.
>
> The bug could be triggered by replacing the following BPF program:
>
> [...]
Here is the summary with links:
- [bpf,1/2] bpf: fix NPE when computing changes_pkt_data of program w/o subprograms
https://git.kernel.org/bpf/bpf/c/ac6542ad9275
- [bpf,2/2] selftests/bpf: extend changes_pkt_data with cases w/o subprograms
https://git.kernel.org/bpf/bpf/c/04789af756a4
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-12-12 19:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 7:07 [PATCH bpf 1/2] bpf: fix NPE when computing changes_pkt_data of program w/o subprograms Eduard Zingerman
2024-12-12 7:07 ` [PATCH bpf 2/2] selftests/bpf: extend changes_pkt_data with cases " Eduard Zingerman
2024-12-12 17:30 ` [PATCH bpf 1/2] bpf: fix NPE when computing changes_pkt_data of program " Alexei Starovoitov
2024-12-12 18:04 ` Eduard Zingerman
2024-12-12 19: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=173403303164.2422426.1574242566292619873.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=dan.carpenter@linaro.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=kernel-team@fb.com \
--cc=lkp@intel.com \
--cc=martin.lau@linux.dev \
--cc=mejedi@gmail.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 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.