From: patchwork-bot+netdevbpf@kernel.org
To: Donggeun Yoo <donggeunyoo.kernel@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, eddyz87@gmail.com, 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, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf v3 0/2] bpf: fix per-cpu initialization of a BPF_F_CPU created hash element
Date: Thu, 24 Sep 2026 14:30:06 +0000 [thread overview]
Message-ID: <179026020640.1578080.12631069595950386099.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260924102321.2120434-1-donggeunyoo.kernel@gmail.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 24 Sep 2026 19:23:19 +0900 you wrote:
> A BPF_F_CPU update that creates a [lru_]percpu_hash element writes the
> named CPU's slot and leaves the others holding the recycled element's
> values, so a lookup of the new key returns a deleted key's per-cpu
> values.
>
> Patch 1 zero-fills the other CPUs. Patch 2 adds the selftest: the
> existing cpu_flag subtests always prime a key with BPF_F_ALL_CPUS
> first, so the create path is not covered today.
>
> [...]
Here is the summary with links:
- [bpf,v3,1/2] bpf: Zero-fill other CPUs when BPF_F_CPU creates a per-cpu hash element
https://git.kernel.org/bpf/bpf/c/c3a66e5f5bab
- [bpf,v3,2/2] selftests/bpf: Test per-cpu initialization of a BPF_F_CPU created element
https://git.kernel.org/bpf/bpf/c/3422808f4e95
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-24 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 10:23 Donggeun Yoo
2026-09-24 10:23 ` [PATCH bpf v3 1/2] bpf: Zero-fill other CPUs when BPF_F_CPU creates a per-cpu " Donggeun Yoo
2026-09-24 10:23 ` [PATCH bpf v3 2/2] selftests/bpf: Test per-cpu initialization of a BPF_F_CPU created element Donggeun Yoo
2026-09-24 14:30 ` patchwork-bot+netdevbpf [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=179026020640.1578080.12631069595950386099.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=donggeunyoo.kernel@gmail.com \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=jolsa@kernel.org \
--cc=leon.hwang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--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
all inboxes | Powered by JetHome®