Re: [PATCH bpf-next v3 0/5] File descriptor interface for BPF streams

[patchwork-bot+netdevbpf@kernel.org]

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Fri, 25 Sep 2026 06:55:27 +0200 you wrote:
> BPF program stdout and stderr streams can currently be consumed only
> through BPF_PROG_STREAM_READ_BY_FD. This requires repeated bpf() calls and
> provides no way to block for output or integrate with poll-based event
> loops.
> 
> Add BPF_PROG_STREAM_OPEN to return a read-only, close-on-exec descriptor
> for a program stream. Reads block by default, with an option for
> non-blocking mode. poll and epoll report readable data and report hangup
> when the program is freed, while allowing buffered data to be drained
> before EOF. Stream descriptors retain the stream storage without retaining
> the program itself. Waiters are notified through irq_work only when a
> publication turns an empty stream readable, as bpf_ringbuf does, so a
> program whose stream nobody drains pays for a single notification.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v3,1/5] bpf: Skip zero-length stream writes
    https://git.kernel.org/bpf/bpf-next/c/f17bedcd2951
  - [bpf-next,v3,2/5] bpf: Add file descriptor interface for program streams
    https://git.kernel.org/bpf/bpf-next/c/e831ff570908
  - [bpf-next,v3,3/5] libbpf: Add bpf_prog_stream_open()
    https://git.kernel.org/bpf/bpf-next/c/9054903ab51b
  - [bpf-next,v3,4/5] bpftool: Add option to wait for program stream output
    https://git.kernel.org/bpf/bpf-next/c/0abecacb4bfd
  - [bpf-next,v3,5/5] selftests/bpf: Test program stream file descriptors
    https://git.kernel.org/bpf/bpf-next/c/4e1d734651e5

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html