From: Liu Jian <liujian56@huawei.com>
To: <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>
Cc: <liujian56@huawei.com>
Subject: [PATCH bpf-next v4 0/3] Enlarge offset check value in bpf_skb_load_bytes
Date: Sat, 16 Apr 2022 18:57:58 +0800 [thread overview]
Message-ID: <20220416105801.88708-1-liujian56@huawei.com> (raw)
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
include/linux/skbuff.h | 2 +-
net/core/filter.c | 4 +-
net/core/skbuff.c | 2 +-
.../selftests/bpf/prog_tests/skb_load_bytes.c | 45 +++++++++++++++++++
.../selftests/bpf/progs/skb_load_bytes.c | 19 ++++++++
5 files changed, 68 insertions(+), 4 deletions(-)
create mode 100644 tools/testing/selftests/bpf/prog_tests/skb_load_bytes.c
create mode 100644 tools/testing/selftests/bpf/progs/skb_load_bytes.c
--
2.17.1
next reply other threads:[~2022-04-16 10:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-16 10:57 Liu Jian [this message]
2022-04-16 10:57 ` [PATCH bpf-next v4 1/3] net: Enlarge offset check value from 0xffff to INT_MAX in bpf_skb_load_bytes 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 ` [PATCH bpf-next v4 0/3] Enlarge offset check value in bpf_skb_load_bytes patchwork-bot+netdevbpf
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=20220416105801.88708-1-liujian56@huawei.com \
--to=liujian56@huawei.com \
--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=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