[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <989e1d04-788d-57c9-9e72-7552e6adc815@fb.com>
Date: Mon, 11 Jul 2022 08:47:50 -0700
From: Yonghong Song <yhs@...com>
To: Matthieu Baerts <matthieu.baerts@...sares.net>,
Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Andrii Nakryiko <andrii@...nel.org>,
Martin KaFai Lau <martin.lau@...ux.dev>,
Song Liu <song@...nel.org>,
John Fastabend <john.fastabend@...il.com>,
KP Singh <kpsingh@...nel.org>,
Stanislav Fomichev <sdf@...gle.com>,
Hao Luo <haoluo@...gle.com>, Jiri Olsa <jolsa@...nel.org>,
Eduard Zingerman <eddyz87@...il.com>
Cc: mptcp@...ts.linux.dev, bpf@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH bpf-next v2] bpf: Fix 'dubious one-bit signed bitfield'
warnings
On 7/11/22 1:12 AM, Matthieu Baerts wrote:
> Our CI[1] reported these warnings when using Sparse:
>
> $ touch net/mptcp/bpf.c
> $ make C=1 net/mptcp/bpf.o
> net/mptcp/bpf.c: note: in included file:
> include/linux/bpf_verifier.h:348:26: error: dubious one-bit signed bitfield
> include/linux/bpf_verifier.h:349:29: error: dubious one-bit signed bitfield
>
> Set them as 'unsigned' to avoid warnings.
>
> [1] https://github.com/multipath-tcp/mptcp_net-next/actions/runs/2643588487
>
> Fixes: 1ade23711971 ("bpf: Inline calls to bpf_loop when callback is known")
> Signed-off-by: Matthieu Baerts <matthieu.baerts@...sares.net>
Acked-by: Yonghong Song <yhs@...com>
Powered by blists - more mailing lists