[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<170303582525.28294.7293109481883503225.git-patchwork-notify@kernel.org>
Date: Wed, 20 Dec 2023 01:30:25 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Menglong Dong <menglong8.dong@...il.com>
Cc: andrii@...nel.org, eddyz87@...il.com, yonghong.song@...ux.dev,
alexei.starovoitov@...il.com, ast@...nel.org, daniel@...earbox.net,
john.fastabend@...il.com, martin.lau@...ux.dev, song@...nel.org,
kpsingh@...nel.org, sdf@...gle.com, haoluo@...gle.com, jolsa@...nel.org,
mykolal@...com, shuah@...nel.org, bpf@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org
Subject: Re: [PATCH bpf-next v5 0/4] bpf: support to track BPF_JNE
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@...nel.org>:
On Tue, 19 Dec 2023 21:47:56 +0800 you wrote:
> For now, the reg bounds is not handled for BPF_JNE case, which can cause
> the failure of following case:
>
> /* The type of "a" is u32 */
> if (a > 0 && a < 100) {
> /* the range of the register for a is [0, 99], not [1, 99],
> * and will cause the following error:
> *
> * invalid zero-sized read
> *
> * as a can be 0.
> */
> bpf_skb_store_bytes(skb, xx, xx, a, 0);
> }
>
> [...]
Here is the summary with links:
- [bpf-next,v5,1/4] bpf: make the verifier tracks the "not equal" for regs
https://git.kernel.org/bpf/bpf-next/c/d028f87517d6
- [bpf-next,v5,2/4] selftests/bpf: remove reduplicated s32 casting in "crafted_cases"
https://git.kernel.org/bpf/bpf-next/c/1de584832375
- [bpf-next,v5,3/4] selftests/bpf: activate the OP_NE logic in range_cond()
https://git.kernel.org/bpf/bpf-next/c/31d9cc96b1e3
- [bpf-next,v5,4/4] selftests/bpf: add testcase to verifier_bounds.c for BPF_JNE
https://git.kernel.org/bpf/bpf-next/c/463ea64eb008
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