From: patchwork-bot+netdevbpf@kernel.org
To: Amery Hung <ameryhung@gmail.com>
Cc: bpf@vger.kernel.org, alexei.starovoitov@gmail.com,
andrii@kernel.org, daniel@iogearbox.net, eddyz87@gmail.com,
memxor@gmail.com, yatsenko@meta.com, kernel-team@meta.com
Subject: Re: [PATCH bpf-next v2 0/5] Task local data bug fixes and improvement
Date: Thu, 02 Apr 2026 22:20:11 +0000 [thread overview]
Message-ID: <177516841154.640064.7942863903383946772.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260331213555.1993883-1-ameryhung@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 31 Mar 2026 14:35:50 -0700 you wrote:
> Hi,
>
> This patchset fixed three task local data bugs, improved the
> memory allocation code, and dropped unnecessary TLD_READ_ONCE. Please
> find the detail in each patch's commit msg.
>
> One thing worth mentioning is that Patch 3 allows us to renable task
> local data selftests as the library now always calls aligned_alloc()
> with size matching alignment under default configuration.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/5] selftests/bpf: Fix task_local_data data allocation size
https://git.kernel.org/bpf/bpf-next/c/7c8ca532a741
- [bpf-next,v2,2/5] selftests/bpf: Simplify task_local_data memory allocation
https://git.kernel.org/bpf/bpf-next/c/bb6d9f5cf1d4
- [bpf-next,v2,3/5] selftests/bpf: Make sure TLD_DEFINE_KEY runs first
https://git.kernel.org/bpf/bpf-next/c/80aa8e9c64d0
- [bpf-next,v2,4/5] selftests/bpf: Remove TLD_READ_ONCE() in the user space header
https://git.kernel.org/bpf/bpf-next/c/0b481a6915ed
- [bpf-next,v2,5/5] selftests/bpf: Improve task local data documentation and fix potential memory leak
https://git.kernel.org/bpf/bpf-next/c/63f5156a9c3e
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-04-02 22:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 21:35 [PATCH bpf-next v2 0/5] Task local data bug fixes and improvement Amery Hung
2026-03-31 21:35 ` [PATCH bpf-next v2 1/5] selftests/bpf: Fix task_local_data data allocation size Amery Hung
2026-04-01 1:48 ` sun jian
2026-03-31 21:35 ` [PATCH bpf-next v2 2/5] selftests/bpf: Simplify task_local_data memory allocation Amery Hung
2026-04-01 1:46 ` sun jian
2026-03-31 21:35 ` [PATCH bpf-next v2 3/5] selftests/bpf: Make sure TLD_DEFINE_KEY runs first Amery Hung
2026-04-01 2:16 ` sun jian
2026-03-31 21:35 ` [PATCH bpf-next v2 4/5] selftests/bpf: Remove TLD_READ_ONCE() in the user space header Amery Hung
2026-04-01 4:22 ` sun jian
2026-03-31 21:35 ` [PATCH bpf-next v2 5/5] selftests/bpf: Improve task local data documentation and fix potential memory leak Amery Hung
2026-04-01 4:11 ` sun jian
2026-04-02 22:20 ` 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=177516841154.640064.7942863903383946772.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=ameryhung@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=kernel-team@meta.com \
--cc=memxor@gmail.com \
--cc=yatsenko@meta.com \
/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