From: Jiri Olsa <olsajiri@gmail.com>
To: Tao Chen <chen.dylane@gmail.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Eduard Zingerman <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
Hou Tao <houtao1@huawei.com>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [v2 PATCH bpf-next 0/2] bpf: Add percpu map value size check
Date: Mon, 9 Sep 2024 11:17:48 +0200 [thread overview]
Message-ID: <Zt69PODgEkg3F1x9@krava> (raw)
In-Reply-To: <20240909071346.1300093-1-chen.dylane@gmail.com>
On Mon, Sep 09, 2024 at 03:13:44PM +0800, Tao Chen wrote:
> Check percpu map value size first and add the test case in selftest.
>
> Change list:
> - v1 -> v2:
> - round up map value size with 8 bytes in patch 1
> - add selftest case in patch 2
>
> Tao Chen (2):
> bpf: Check percpu map value size first
> bpf/selftests: Check errno when percpu map value size exceeds
lgtm
Acked-by: Jiri Olsa <jolsa@kernel.org>
jirka
>
> kernel/bpf/arraymap.c | 3 ++
> kernel/bpf/hashtab.c | 3 ++
> .../selftests/bpf/prog_tests/map_init.c | 32 +++++++++++++++++++
> .../selftests/bpf/progs/test_map_init.c | 6 ++++
> 4 files changed, 44 insertions(+)
>
> --
> 2.25.1
>
>
prev parent reply other threads:[~2024-09-09 9:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 7:13 [v2 PATCH bpf-next 0/2] bpf: Add percpu map value size check Tao Chen
2024-09-09 7:13 ` [v2 PATCH bpf-next 1/2] bpf: Check percpu map value size first Tao Chen
2024-09-09 20:17 ` Andrii Nakryiko
2024-09-10 2:35 ` Tao Chen
2024-09-09 7:13 ` [v2 PATCH bpf-next 2/2] bpf/selftests: Check errno when percpu map value size exceeds Tao Chen
2024-09-09 20:16 ` Andrii Nakryiko
2024-09-10 2:40 ` Tao Chen
2024-09-09 9:17 ` Jiri Olsa [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=Zt69PODgEkg3F1x9@krava \
--to=olsajiri@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chen.dylane@gmail.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=houtao1@huawei.com \
--cc=john.fastabend@gmail.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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