From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yhs@fb.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kernel-team@fb.com, martin.lau@kernel.org,
lkp@intel.com, error27@gmail.com, nathan@kernel.org
Subject: Re: [PATCH bpf-next] bpf: Fix a BTF_ID_LIST bug with CONFIG_DEBUG_INFO_BTF not set
Date: Wed, 23 Nov 2022 21:30:15 +0000 [thread overview]
Message-ID: <166923901573.7482.12330550666164946305.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221123155759.2669749-1-yhs@fb.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 23 Nov 2022 07:57:59 -0800 you wrote:
> With CONFIG_DEBUG_INFO_BTF not set, we hit the following compilation error,
> /.../kernel/bpf/verifier.c:8196:23: error: array index 6 is past the end of the array
> (that has type 'u32[5]' (aka 'unsigned int[5]')) [-Werror,-Warray-bounds]
> if (meta->func_id == special_kfunc_list[KF_bpf_cast_to_kern_ctx])
> ^ ~~~~~~~~~~~~~~~~~~~~~~~
> /.../kernel/bpf/verifier.c:8174:1: note: array 'special_kfunc_list' declared here
> BTF_ID_LIST(special_kfunc_list)
> ^
> /.../include/linux/btf_ids.h:207:27: note: expanded from macro 'BTF_ID_LIST'
> #define BTF_ID_LIST(name) static u32 __maybe_unused name[5];
> ^
> /.../kernel/bpf/verifier.c:8443:19: error: array index 5 is past the end of the array
> (that has type 'u32[5]' (aka 'unsigned int[5]')) [-Werror,-Warray-bounds]
> btf_id == special_kfunc_list[KF_bpf_list_pop_back];
> ^ ~~~~~~~~~~~~~~~~~~~~
> /.../kernel/bpf/verifier.c:8174:1: note: array 'special_kfunc_list' declared here
> BTF_ID_LIST(special_kfunc_list)
> ^
> /.../include/linux/btf_ids.h:207:27: note: expanded from macro 'BTF_ID_LIST'
> #define BTF_ID_LIST(name) static u32 __maybe_unused name[5];
> ...
>
> [...]
Here is the summary with links:
- [bpf-next] bpf: Fix a BTF_ID_LIST bug with CONFIG_DEBUG_INFO_BTF not set
https://git.kernel.org/bpf/bpf-next/c/beb3d47d1d3d
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-11-23 21:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 15:57 [PATCH bpf-next] bpf: Fix a BTF_ID_LIST bug with CONFIG_DEBUG_INFO_BTF not set Yonghong Song
2022-11-23 21:23 ` Alexei Starovoitov
2022-11-23 21: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=166923901573.7482.12330550666164946305.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=error27@gmail.com \
--cc=kernel-team@fb.com \
--cc=lkp@intel.com \
--cc=martin.lau@kernel.org \
--cc=nathan@kernel.org \
--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