From: Masoud Aghasi <maghasi@disroot.org>
To: bpf@vger.kernel.org
Cc: andrii@kernel.org, eddyz87@gmail.com, ast@kernel.org,
daniel@iogearbox.net, memxor@gmail.com, martin.lau@linux.dev,
song@kernel.org, yonghong.song@linux.dev, jolsa@kernel.org,
emil@etsalapatis.com, ihor.solodrai@linux.dev,
leon.hwang@linux.dev, Masoud Aghasi <maghasi@disroot.org>
Subject: [PATCH v2 2/2] selftests/bpf: add test for percpu map flags combination
Date: Wed, 30 Sep 2026 14:57:53 +0100 [thread overview]
Message-ID: <20260930135753.1063495-3-maghasi@disroot.org> (raw)
In-Reply-To: <20260930135753.1063495-1-maghasi@disroot.org>
Add tests to exercise usage of a combination of flags for
percpu hash map updates.
Before the fix, these tests fail to respect user flags combination of
(BPF_F_CPU | BPF_EXIST). With the fix applied these tests pass.
Signed-off-by: Masoud Aghasi <maghasi@disroot.org>
---
.../selftests/bpf/prog_tests/percpu_alloc.c | 32 +++++++++++++++++++
1 file changed, 32 insertions(+)
diff --git a/tools/testing/selftests/bpf/prog_tests/percpu_alloc.c b/tools/testing/selftests/bpf/prog_tests/percpu_alloc.c
index 7b4a1e24363b..e14a476da5c8 100644
--- a/tools/testing/selftests/bpf/prog_tests/percpu_alloc.c
+++ b/tools/testing/selftests/bpf/prog_tests/percpu_alloc.c
@@ -537,6 +537,34 @@ static void test_hash_cpu_flag(void)
test_map_op_cpu_flag(BPF_MAP_TYPE_HASH);
}
+static void test_percpu_map_flags_combination(enum bpf_map_type map_type)
+{
+ u32 max_entries = 1;
+ u64 flags, val = 0;
+ int err, map_fd, key = 0;
+
+ map_fd = bpf_map_create(map_type, "test_flags_combo",
+ sizeof(int), sizeof(u64), max_entries, NULL);
+ if (!ASSERT_GE(map_fd, 0, "bpf_map_create"))
+ return;
+
+ flags = BPF_F_CPU | BPF_EXIST;
+ err = bpf_map_update_elem(map_fd, &key, &val, flags);
+ ASSERT_EQ(err, -ENOENT, "bpf_map_update_elem flags_combo");
+
+ close(map_fd);
+}
+
+static void test_percpu_hash_flags_combination(void)
+{
+ test_percpu_map_flags_combination(BPF_MAP_TYPE_PERCPU_HASH);
+}
+
+static void test_percpu_lru_hash_flags_combination(void)
+{
+ test_percpu_map_flags_combination(BPF_MAP_TYPE_LRU_PERCPU_HASH);
+}
+
void test_percpu_alloc(void)
{
if (test__start_subtest("array"))
@@ -565,4 +593,8 @@ void test_percpu_alloc(void)
test_array_cpu_flag();
if (test__start_subtest("cpu_flag_hash"))
test_hash_cpu_flag();
+ if (test__start_subtest("percpu_hash_flags_combination"))
+ test_percpu_hash_flags_combination();
+ if (test__start_subtest("percpu_lru_hash_flags_combination"))
+ test_percpu_lru_hash_flags_combination();
}
--
2.47.3
next prev parent reply other threads:[~2026-09-30 13:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 13:57 [PATCH v2 0/2] bpf: Fix incorrect handling of user flags by percpu map updates Masoud Aghasi
2026-09-30 13:57 ` [PATCH v2 1/2] " Masoud Aghasi
2026-10-01 15:16 ` Leon Hwang
2026-10-02 5:34 ` Masoud Aghasi
2026-09-30 13:57 ` Masoud Aghasi [this message]
2026-09-30 14:42 ` [PATCH v2 2/2] selftests/bpf: add test for percpu map flags combination bot+bpf-ci
2026-10-01 15:17 ` Leon Hwang
2026-10-02 5:36 ` Masoud Aghasi
2026-10-01 15:37 ` Alexei Starovoitov
2026-10-02 5:45 ` Masoud Aghasi
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=20260930135753.1063495-3-maghasi@disroot.org \
--to=maghasi@disroot.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=jolsa@kernel.org \
--cc=leon.hwang@linux.dev \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--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