From: patchwork-bot+netdevbpf@kernel.org
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: bpf@vger.kernel.org, oliver.sang@intel.com
Subject: Re: [PATCH bpf-next] bpf: Check for NULL return from bpf_get_btf_vmlinux
Date: Mon, 21 Mar 2022 02:30:10 +0000 [thread overview]
Message-ID: <164782981036.13314.5384980131744260251.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220320143003.589540-1-memxor@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sun, 20 Mar 2022 20:00:03 +0530 you wrote:
> When CONFIG_DEBUG_INFO_BTF is disabled, bpf_get_btf_vmlinux can return a
> NULL pointer. Check for it in btf_get_module_btf to prevent a NULL pointer
> dereference.
>
> While kernel test robot only complained about this specific case, let's
> also check for NULL in other call sites of bpf_get_btf_vmlinux.
>
> [...]
Here is the summary with links:
- [bpf-next] bpf: Check for NULL return from bpf_get_btf_vmlinux
https://git.kernel.org/bpf/bpf-next/c/7ada3787e91c
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-03-21 2:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-20 14:30 [PATCH bpf-next] bpf: Check for NULL return from bpf_get_btf_vmlinux Kumar Kartikeya Dwivedi
2022-03-21 2: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=164782981036.13314.5384980131744260251.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=memxor@gmail.com \
--cc=oliver.sang@intel.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