Hello:
This series was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <[email protected]>:
On Sun, 23 Aug 2026 22:17:24 +0800 you wrote:
> bpf_stream_push_str() accounts the string length before allocating a
> stream element. If the allocation fails, the length remains charged even
> though no element is queued and therefore cannot be released by a reader.
> Repeated failures can exhaust the stream capacity permanently until the
> BPF program is freed.
>
> Refactor bpf_stream_release_capacity() to take a length so the consume
> and release sides are symmetric, and use it to roll back the charge when
> creating the stream element fails.
>
> [...]
Here is the summary with links:
- [bpf-next,v4,1/5] bpf: roll back stream capacity when allocation fails
https://git.kernel.org/bpf/bpf-next/c/bd2466ed8fc2
- [bpf-next,v4,2/5] bpf: fix stream capacity leak in staging path
https://git.kernel.org/bpf/bpf-next/c/effa6370ba89
- [bpf-next,v4,3/5] bpf: return partial progress from bpf_stream_read on fault
https://git.kernel.org/bpf/bpf-next/c/16790357a50b
- [bpf-next,v4,4/5] bpf: reject oversized bpf_stream_vprintk output with
-E2BIG
https://git.kernel.org/bpf/bpf-next/c/41c0348f6e65
- [bpf-next,v4,5/5] selftests/bpf: cover stream capacity and partial read
edge cases
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
