From: Yonghong Song <yonghong.song@linux.dev>
To: "Jose E. Marchesi" <jose.marchesi@oracle.com>, bpf@vger.kernel.org
Cc: david.faust@oracle.com, cupertino.miranda@oracle.com,
Eduard Zingerman <eddyz87@gmail.com>
Subject: Re: [PATCH bpf-next] bpf: avoid uninitialized value in BPF_CORE_READ_BITFIELD
Date: Tue, 7 May 2024 09:23:31 -0700 [thread overview]
Message-ID: <263a563a-3abe-4c88-8a1e-e10fb8a6dfad@linux.dev> (raw)
In-Reply-To: <20240507113950.28208-1-jose.marchesi@oracle.com>
On 5/7/24 4:39 AM, Jose E. Marchesi wrote:
> GCC warns that `val' may be used uninitialized in the
> BPF_CORE_READ_BITFIELD macro, defined in bpf_core_read.h as:
>
> [...]
> unsigned long long val; \
> [...] \
> switch (__CORE_RELO(s, field, BYTE_SIZE)) { \
> case 1: val = *(const unsigned char *)p; break; \
> case 2: val = *(const unsigned short *)p; break; \
> case 4: val = *(const unsigned int *)p; break; \
> case 8: val = *(const unsigned long long *)p; break; \
> } \
> [...]
> val; \
> } \
>
> This patch initializes `val' to zero in order to avoid the warning,
> and random values to be used in case __builtin_preserve_field_info
> returns unexpected values for BPF_FIELD_BYTE_SIZE.
In clang, __builtin_preserve_field_info either returns correct value
or caused compilation error. Do you mean for gcc __builtin_preserve_field_info
might return an unexpected value here?
BTW, your change makes sense to silent this warning. So Ack below.
>
> Tested in bpf-next master.
> No regressions.
>
> Signed-off-by: Jose E. Marchesi <jose.marchesi@oracle.com>
> Cc: david.faust@oracle.com
> Cc: cupertino.miranda@oracle.com
> Cc: Eduard Zingerman <eddyz87@gmail.com>
> Cc: Yonghong Song <yonghong.song@linux.dev>
Acked-by: Yonghong Song <yonghong.song@linux.dev>
> ---
> tools/lib/bpf/bpf_core_read.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/lib/bpf/bpf_core_read.h b/tools/lib/bpf/bpf_core_read.h
> index b5c7ce5c243a..88d129b5f0a1 100644
> --- a/tools/lib/bpf/bpf_core_read.h
> +++ b/tools/lib/bpf/bpf_core_read.h
> @@ -89,7 +89,7 @@ enum bpf_enum_value_kind {
> */
> #define BPF_CORE_READ_BITFIELD(s, field) ({ \
> const void *p = (const void *)s + __CORE_RELO(s, field, BYTE_OFFSET); \
> - unsigned long long val; \
> + unsigned long long val = 0; \
> \
> /* This is a so-called barrier_var() operation that makes specified \
> * variable "a black box" for optimizing compiler. \
next prev parent reply other threads:[~2024-05-07 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 11:39 [PATCH bpf-next] bpf: avoid uninitialized value in BPF_CORE_READ_BITFIELD Jose E. Marchesi
2024-05-07 16:23 ` Yonghong Song [this message]
2024-05-07 18:13 ` Jose E. Marchesi
2024-05-07 16:41 ` Andrii Nakryiko
2024-05-07 18:14 ` Jose E. Marchesi
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=263a563a-3abe-4c88-8a1e-e10fb8a6dfad@linux.dev \
--to=yonghong.song@linux.dev \
--cc=bpf@vger.kernel.org \
--cc=cupertino.miranda@oracle.com \
--cc=david.faust@oracle.com \
--cc=eddyz87@gmail.com \
--cc=jose.marchesi@oracle.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