BPF List
 help / color / mirror / Atom feed
From: Tao Chen <chen.dylane@gmail.com>
To: 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>
Cc: Tao Chen <chen.dylane@gmail.com>,
	bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [v3 PATCH bpf-next 0/2] bpf: Add percpu map value size check
Date: Tue, 10 Sep 2024 22:41:09 +0800	[thread overview]
Message-ID: <20240910144111.1464912-1-chen.dylane@gmail.com> (raw)

Check percpu map value size first and add the test case in selftest.

Change list:
- v2 -> v3:
    - use bpf_map_create API and mv test case in map_percpu_stats.c
- 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

 kernel/bpf/arraymap.c                          |  3 +++
 kernel/bpf/hashtab.c                           |  3 +++
 .../selftests/bpf/map_tests/map_percpu_stats.c | 18 ++++++++++++++++++
 3 files changed, 24 insertions(+)

-- 
2.43.0


             reply	other threads:[~2024-09-10 14:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-10 14:41 Tao Chen [this message]
2024-09-10 14:41 ` [v3 PATCH bpf-next 1/2] bpf: Check percpu map value size first Tao Chen
2024-09-10 14:41 ` [v3 PATCH bpf-next 2/2] bpf/selftests: Check errno when percpu map value size exceeds Tao Chen
2024-09-11 20:30 ` [v3 PATCH bpf-next 0/2] bpf: Add percpu map value size check 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=20240910144111.1464912-1-chen.dylane@gmail.com \
    --to=chen.dylane@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --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