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 v1 0/3] Fix garbage data in task local data
Date: Wed, 15 Apr 2026 19:20:20 +0000 [thread overview]
Message-ID: <177628082028.2402333.10439843576441587011.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260413190259.358442-1-ameryhung@gmail.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 13 Apr 2026 12:02:56 -0700 you wrote:
> Hi,
>
> The patchset fixes two scenarios where BPF side task local data API may
> see garbage data and adds corresponding selftests.
>
>
> Amery Hung (3):
> selftests/bpf: Prevent allocating data larger than a page
> selftests/bpf: Fix tld_get_data() returning garbage data
> selftests/bpf: Test small task local data allocation
>
> [...]
Here is the summary with links:
- [bpf-next,v1,1/3] selftests/bpf: Prevent allocating data larger than a page
https://git.kernel.org/bpf/bpf/c/36bf7beb9d23
- [bpf-next,v1,2/3] selftests/bpf: Fix tld_get_data() returning garbage data
https://git.kernel.org/bpf/bpf/c/615e55a24184
- [bpf-next,v1,3/3] selftests/bpf: Test small task local data allocation
https://git.kernel.org/bpf/bpf/c/b4b0233730d5
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-15 19:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 19:02 [PATCH bpf-next v1 0/3] Fix garbage data in task local data Amery Hung
2026-04-13 19:02 ` [PATCH bpf-next v1 1/3] selftests/bpf: Prevent allocating data larger than a page Amery Hung
2026-04-13 19:02 ` [PATCH bpf-next v1 2/3] selftests/bpf: Fix tld_get_data() returning garbage data Amery Hung
2026-04-13 19:02 ` [PATCH bpf-next v1 3/3] selftests/bpf: Test small task local data allocation Amery Hung
2026-04-15 19: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=177628082028.2402333.10439843576441587011.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