From: Yonghong Song <yhs@fb.com>
To: Andrii Nakryiko <andrii@kernel.org>,
bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net
Cc: kernel-team@fb.com
Subject: Re: [PATCH v2 bpf-next 0/4] BPF array map fixes and improvements
Date: Fri, 15 Jul 2022 09:29:17 -0700 [thread overview]
Message-ID: <3e4bbe32-c516-8391-0ee2-7b2d1c5207ca@fb.com> (raw)
In-Reply-To: <20220715053146.1291891-1-andrii@kernel.org>
On 7/14/22 10:31 PM, Andrii Nakryiko wrote:
> Fix 32-bit overflow in value pointer calculations in BPF array map. And then
> raise obsolete limit on array map value size. Add selftest making sure this is
> working as intended.
>
> v1->v2:
> - fix broken patch #1 (no mask_index use in helper, as stated in commit
> message; and add missing semicolon).
>
> Andrii Nakryiko (4):
> bpf: fix potential 32-bit overflow when accessing ARRAY map element
> bpf: make uniform use of array->elem_size everywhere in arraymap.c
> bpf: remove obsolete KMALLOC_MAX_SIZE restriction on array map value
> size
> selftests/bpf: validate .bss section bigger than 8MB is possible now
>
> kernel/bpf/arraymap.c | 40 ++++++++++---------
> .../selftests/bpf/prog_tests/skeleton.c | 2 +
> .../selftests/bpf/progs/test_skeleton.c | 4 ++
> 3 files changed, 28 insertions(+), 18 deletions(-)
>
Ack for the whole series.
Acked-by: Yonghong Song <yhs@fb.com>
next prev parent reply other threads:[~2022-07-15 16:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 5:31 [PATCH v2 bpf-next 0/4] BPF array map fixes and improvements Andrii Nakryiko
2022-07-15 5:31 ` [PATCH v2 bpf-next 1/4] bpf: fix potential 32-bit overflow when accessing ARRAY map element Andrii Nakryiko
2022-07-15 5:31 ` [PATCH v2 bpf-next 2/4] bpf: make uniform use of array->elem_size everywhere in arraymap.c Andrii Nakryiko
2022-07-15 5:31 ` [PATCH v2 bpf-next 3/4] bpf: remove obsolete KMALLOC_MAX_SIZE restriction on array map value size Andrii Nakryiko
2022-07-15 5:31 ` [PATCH v2 bpf-next 4/4] selftests/bpf: validate .bss section bigger than 8MB is possible now Andrii Nakryiko
2022-07-15 16:29 ` Yonghong Song [this message]
2022-07-19 16:50 ` [PATCH v2 bpf-next 0/4] BPF array map fixes and improvements 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=3e4bbe32-c516-8391-0ee2-7b2d1c5207ca@fb.com \
--to=yhs@fb.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@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