From: patchwork-bot+netdevbpf@kernel.org
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, eddyz87@gmail.com, emil@etsalapatis.com,
npc@anthropic.com, kkd@meta.com, kernel-team@meta.com
Subject: Re: [PATCH bpf v2 0/8] Misc bug fixes - part 3
Date: Fri, 04 Sep 2026 15:00:17 +0000 [thread overview]
Message-ID: <178853401764.323612.13062376369096458140.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260904084325.52250-1-memxor@gmail.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 4 Sep 2026 10:43:13 +0200 you wrote:
> A set of miscellaneous fixes for bugs reported by Nicholas, batched
> together again. See commit logs for details. Some of this was caught and
> posted by Ning before, but AI raised some concerns, so I'm resolving
> those issues and commandeering their patches now.
>
> Changelog:
>
> [...]
Here is the summary with links:
- [bpf,v2,1/8] bpf: Require MEM_PERCPU for percpu kptr stores
https://git.kernel.org/bpf/bpf/c/048029ba1c79
- [bpf,v2,2/8] selftests/bpf: Reject non-percpu values in percpu kptr fields
https://git.kernel.org/bpf/bpf/c/17487b31f479
- [bpf,v2,3/8] bpf: Keep refcount_acquire nullable for borrowed RCU kptrs
https://git.kernel.org/bpf/bpf/c/dc36739e5cc9
- [bpf,v2,4/8] selftests/bpf: Test borrowed refcount acquisition nullability
https://git.kernel.org/bpf/bpf/c/2edd8339468e
- [bpf,v2,5/8] bpf: Clear NON_OWN_REF after RCU protection ends
https://git.kernel.org/bpf/bpf/c/cd6f72d7f38e
- [bpf,v2,6/8] selftests/bpf: Reject graph kptr use after RCU unlock
https://git.kernel.org/bpf/bpf/c/6668ed271eae
- [bpf,v2,7/8] bpf: Reject untrusted allocated-object pointers
https://git.kernel.org/bpf/bpf/c/7441ee827664
- [bpf,v2,8/8] selftests/bpf: Reject refcount acquisition after RCU unlock
https://git.kernel.org/bpf/bpf/c/9492baf8532c
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-04 15:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 8:43 [PATCH bpf v2 0/8] Misc bug fixes - part 3 Kumar Kartikeya Dwivedi
2026-09-04 8:43 ` [PATCH bpf v2 1/8] bpf: Require MEM_PERCPU for percpu kptr stores Kumar Kartikeya Dwivedi
2026-09-04 8:43 ` [PATCH bpf v2 2/8] selftests/bpf: Reject non-percpu values in percpu kptr fields Kumar Kartikeya Dwivedi
2026-09-04 8:43 ` [PATCH bpf v2 3/8] bpf: Keep refcount_acquire nullable for borrowed RCU kptrs Kumar Kartikeya Dwivedi
2026-09-04 8:43 ` [PATCH bpf v2 4/8] selftests/bpf: Test borrowed refcount acquisition nullability Kumar Kartikeya Dwivedi
2026-09-04 9:47 ` bot+bpf-ci
2026-09-04 8:43 ` [PATCH bpf v2 5/8] bpf: Clear NON_OWN_REF after RCU protection ends Kumar Kartikeya Dwivedi
2026-09-04 8:43 ` [PATCH bpf v2 6/8] selftests/bpf: Reject graph kptr use after RCU unlock Kumar Kartikeya Dwivedi
2026-09-04 8:43 ` [PATCH bpf v2 7/8] bpf: Reject untrusted allocated-object pointers Kumar Kartikeya Dwivedi
2026-09-04 8:43 ` [PATCH bpf v2 8/8] selftests/bpf: Reject refcount acquisition after RCU unlock Kumar Kartikeya Dwivedi
2026-09-04 15:00 ` 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=178853401764.323612.13062376369096458140.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=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=kernel-team@meta.com \
--cc=kkd@meta.com \
--cc=memxor@gmail.com \
--cc=npc@anthropic.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.