From: patchwork-bot+netdevbpf@kernel.org
To: Stanislav Fomichev <sdf@google.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
haoluo@google.com, jolsa@kernel.org,
syzbot+0f8d989b1fba1addc5e0@syzkaller.appspotmail.com
Subject: Re: [PATCH bpf-next] bpf: Check attach_func_proto more carefully in check_helper_call
Date: Thu, 21 Jul 2022 13:30:13 +0000 [thread overview]
Message-ID: <165841021395.31007.4261003933380275884.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220720164729.147544-1-sdf@google.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Wed, 20 Jul 2022 09:47:29 -0700 you wrote:
> Syzkaller found a problem similar to d1a6edecc1fd ("bpf: Check
> attach_func_proto more carefully in check_return_code") where
> attach_func_proto might be NULL:
>
> RIP: 0010:check_helper_call+0x3dcb/0x8d50 kernel/bpf/verifier.c:7330
> do_check kernel/bpf/verifier.c:12302 [inline]
> do_check_common+0x6e1e/0xb980 kernel/bpf/verifier.c:14610
> do_check_main kernel/bpf/verifier.c:14673 [inline]
> bpf_check+0x661e/0xc520 kernel/bpf/verifier.c:15243
> bpf_prog_load+0x11ae/0x1f80 kernel/bpf/syscall.c:2620
>
> [...]
Here is the summary with links:
- [bpf-next] bpf: Check attach_func_proto more carefully in check_helper_call
https://git.kernel.org/bpf/bpf-next/c/aef9d4a34a51
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:[~2022-07-21 13:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 16:47 [PATCH bpf-next] bpf: Check attach_func_proto more carefully in check_helper_call Stanislav Fomichev
2022-07-20 18:16 ` Martin KaFai Lau
2022-07-21 13:30 ` 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=165841021395.31007.4261003933380275884.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=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=syzbot+0f8d989b1fba1addc5e0@syzkaller.appspotmail.com \
--cc=yhs@fb.com \
/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