From: patchwork-bot+netdevbpf@kernel.org
To: Liu Jian <liujian56@huawei.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org,
davem@davemloft.net, kuba@kernel.org, sdf@google.com,
netdev@vger.kernel.org, bpf@vger.kernel.org, pabeni@redhat.com
Subject: Re: [PATCH bpf-next v4 0/3] Enlarge offset check value in bpf_skb_load_bytes
Date: Wed, 20 Apr 2022 21:50:27 +0000 [thread overview]
Message-ID: <165049142756.27071.2282139380669338907.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220416105801.88708-1-liujian56@huawei.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.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
prev parent reply other threads:[~2022-04-20 21:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-16 10:57 [PATCH bpf-next v4 0/3] Enlarge offset check value in bpf_skb_load_bytes Liu Jian
2022-04-16 10:57 ` [PATCH bpf-next v4 1/3] net: Enlarge offset check value from 0xffff to INT_MAX " Liu Jian
2022-04-16 10:58 ` [PATCH bpf-next v4 2/3] net: change skb_ensure_writable()'s write_len param to unsigned int type Liu Jian
2022-04-16 10:58 ` [PATCH bpf-next v4 3/3] selftests: bpf: add test for skb_load_bytes Liu Jian
2022-04-20 21:50 ` patchwork-bot+netdevbpf [this message]
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=165049142756.27071.2282139380669338907.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=liujian56@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@google.com \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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