[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <165049142756.27071.2282139380669338907.git-patchwork-notify@kernel.org>
Date: Wed, 20 Apr 2022 21:50:27 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Liu Jian <liujian56@...wei.com>
Cc: ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
kafai@...com, songliubraving@...com, yhs@...com,
john.fastabend@...il.com, kpsingh@...nel.org, davem@...emloft.net,
kuba@...nel.org, sdf@...gle.com, netdev@...r.kernel.org,
bpf@...r.kernel.org, pabeni@...hat.com
Subject: Re: [PATCH bpf-next v4 0/3] Enlarge offset check value in
bpf_skb_load_bytes
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@...earbox.net>:
On Sat, 16 Apr 2022 18:57:58 +0800 you wrote:
> The data length of skb frags + frag_list may be greater than 0xffff,
> and skb_header_pointer can not handle negative offset.
> So here INT_MAX is used to check the validity of offset.
>
> And add the test case for the change.
>
> Liu Jian (3):
> net: Enlarge offset check value from 0xffff to INT_MAX in
> bpf_skb_load_bytes
> net: change skb_ensure_writable()'s write_len param to unsigned int
> type
> selftests: bpf: add test for skb_load_bytes
>
> [...]
Here is the summary with links:
- [bpf-next,v4,1/3] net: Enlarge offset check value from 0xffff to INT_MAX in bpf_skb_load_bytes
https://git.kernel.org/bpf/bpf-next/c/45969b4152c1
- [bpf-next,v4,2/3] net: change skb_ensure_writable()'s write_len param to unsigned int type
https://git.kernel.org/bpf/bpf-next/c/92ece28072f1
- [bpf-next,v4,3/3] selftests: bpf: add test for skb_load_bytes
https://git.kernel.org/bpf/bpf-next/c/127e7dca427b
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