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,
ihor.solodrai@linux.dev, kkd@meta.com, kernel-team@meta.com
Subject: Re: [PATCH bpf-next v1 0/6] Fix ring buffer callback consumption
Date: Mon, 09 Nov 2026 23:00:09 +0000 [thread overview]
Message-ID: <179426520918.3532311.3624579682488216373.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1794253561.git.memxor@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:
On Mon, 9 Nov 2026 20:47:26 +0100 you wrote:
> Commandeering some patches from Tamir for libbpf ringbuf callback
> consumption fixes. See commit logs for details.
>
> Tamir Duberstein (6):
> libbpf: Honor zero consume bounds
> libbpf: Prevent NULL callback crash
> libbpf: Reject overwrite callback use
> selftests/bpf: Test ring buffer consumption with a zero bound
> selftests/bpf: Test the ring buffer consumer with a NULL sample
> callback
> selftests/bpf: Test that callbacks reject an overwritable ring buffer
>
> [...]
Here is the summary with links:
- [bpf-next,v1,1/6] libbpf: Honor zero consume bounds
https://git.kernel.org/bpf/bpf-next/c/40edacd47993
- [bpf-next,v1,2/6] libbpf: Prevent NULL callback crash
https://git.kernel.org/bpf/bpf-next/c/c0628a0659b6
- [bpf-next,v1,3/6] libbpf: Reject overwrite callback use
https://git.kernel.org/bpf/bpf-next/c/f756eedb24d4
- [bpf-next,v1,4/6] selftests/bpf: Test ring buffer consumption with a zero bound
https://git.kernel.org/bpf/bpf-next/c/c82153312a0a
- [bpf-next,v1,5/6] selftests/bpf: Test the ring buffer consumer with a NULL sample callback
https://git.kernel.org/bpf/bpf-next/c/21f96738feb7
- [bpf-next,v1,6/6] selftests/bpf: Test that callbacks reject an overwritable ring buffer
https://git.kernel.org/bpf/bpf-next/c/249c9bb9f3ac
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-11-09 23:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 19:47 [PATCH bpf-next v1 0/6] Fix ring buffer callback consumption Kumar Kartikeya Dwivedi
2026-11-09 19:47 ` [PATCH bpf-next v1 1/6] libbpf: Honor zero consume bounds Kumar Kartikeya Dwivedi
2026-11-09 19:47 ` [PATCH bpf-next v1 2/6] libbpf: Prevent NULL callback crash Kumar Kartikeya Dwivedi
2026-11-09 19:47 ` [PATCH bpf-next v1 3/6] libbpf: Reject overwrite callback use Kumar Kartikeya Dwivedi
2026-11-09 19:47 ` [PATCH bpf-next v1 4/6] selftests/bpf: Test ring buffer consumption with a zero bound Kumar Kartikeya Dwivedi
2026-11-09 19:47 ` [PATCH bpf-next v1 5/6] selftests/bpf: Test the ring buffer consumer with a NULL sample callback Kumar Kartikeya Dwivedi
2026-11-09 19:47 ` [PATCH bpf-next v1 6/6] selftests/bpf: Test that callbacks reject an overwritable ring buffer Kumar Kartikeya Dwivedi
2026-11-09 23: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=179426520918.3532311.3624579682488216373.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=ihor.solodrai@linux.dev \
--cc=kernel-team@meta.com \
--cc=kkd@meta.com \
--cc=memxor@gmail.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