From: Masoud Aghasi <maghasi@disroot.org>
To: Leon Hwang <leon.hwang@linux.dev>, 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
Subject: Re: [PATCH v2 2/2] selftests/bpf: add test for percpu map flags combination
Date: Fri, 2 Oct 2026 06:36:00 +0100 [thread overview]
Message-ID: <ce867a52-b008-4ee2-93ca-52a9443d3a9d@disroot.org> (raw)
In-Reply-To: <9d233b9f-4eb4-4550-8dfa-f56b2b6492ad@linux.dev>
On 01/10/2026 16:17, Leon Hwang wrote:
> On 2026/9/30 21:57, Masoud Aghasi wrote:
>> 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.
>
> I think combinations of (BPF_F_CPU, BPF_F_ALL_CPUS) and (BPF_EXIST,
> BPF_NOEXIST) should be covered for all per-CPU map types where applicable.
>
> Thanks,
> Leon
>
>> [...]
>
Thanks.
I will add full test coverage for these to v3.
next prev parent reply other threads:[~2026-10-02 5:36 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 ` [PATCH v2 2/2] selftests/bpf: add test for percpu map flags combination Masoud Aghasi
2026-09-30 14:42 ` bot+bpf-ci
2026-10-01 15:17 ` Leon Hwang
2026-10-02 5:36 ` Masoud Aghasi [this message]
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=ce867a52-b008-4ee2-93ca-52a9443d3a9d@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