[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id:
<172556883729.1838815.11480197558494188207.git-patchwork-notify@kernel.org>
Date: Thu, 05 Sep 2024 20:40:37 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Shung-Hsi Yu <shung-hsi.yu@...e.com>
Cc: eddyz87@...il.com, bpf@...r.kernel.org, ast@...nel.org,
daniel@...earbox.net, andrii@...nel.org, martin.lau@...ux.dev,
song@...nel.org, yonghong.song@...ux.dev, john.fastabend@...il.com,
kpsingh@...nel.org, sdf@...ichev.me, haoluo@...gle.com, jolsa@...nel.org,
davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
void@...ifault.com, netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
lkp@...el.com
Subject: Re: [PATCH bpf-next] bpf: use type_may_be_null() helper for
nullable-param check
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@...nel.org>:
On Thu, 5 Sep 2024 13:52:32 +0800 you wrote:
> Commit 980ca8ceeae6 ("bpf: check bpf_dummy_struct_ops program params for
> test runs") does bitwise AND between reg_type and PTR_MAYBE_NULL, which
> is correct, but due to type difference the compiler complains:
>
> net/bpf/bpf_dummy_struct_ops.c:118:31: warning: bitwise operation between different enumeration types ('const enum bpf_reg_type' and 'enum bpf_type_flag') [-Wenum-enum-conversion]
> 118 | if (info && (info->reg_type & PTR_MAYBE_NULL))
> | ~~~~~~~~~~~~~~ ^ ~~~~~~~~~~~~~~
>
> [...]
Here is the summary with links:
- [bpf-next] bpf: use type_may_be_null() helper for nullable-param check
https://git.kernel.org/bpf/bpf-next/c/1ae497c78f01
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists