[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <166567561608.22924.7276455354921254094.git-patchwork-notify@kernel.org>
Date: Thu, 13 Oct 2022 15:40:16 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: David Vernet <void@...ifault.com>
Cc: bpf@...r.kernel.org, andrii@...nel.org, ast@...nel.org,
martin.lau@...ux.dev, daniel@...earbox.net, song@...nel.org,
yhs@...com, john.fastabend@...il.com, kpsingh@...nel.org,
sdf@...gle.com, haoluo@...gle.com, jolsa@...nel.org,
linux-kernel@...r.kernel.org, kernel-team@...com
Subject: Re: [PATCH 0/2] Allow bpf_user_ringbuf_drain() callbacks to return 1
Hello:
This series was applied to bpf/bpf.git (master)
by Andrii Nakryiko <andrii@...nel.org>:
On Wed, 12 Oct 2022 18:20:13 -0500 you wrote:
> The bpf_user_ringbuf_drain() helper function allows a BPF program to
> specify a callback that is invoked when draining entries from a
> BPF_MAP_TYPE_USER_RINGBUF ring buffer map. The API is meant to allow the
> callback to return 0 if it wants to continue draining samples, and 1 if
> it's done draining. Unfortunately, bpf_user_ringbuf_drain() landed shortly
> after commit 1bfe26fb0827 ("bpf: Add verifier support for custom
> callback return range"), which changed the default behavior of callbacks
> to only support returning 0, and the corresponding necessary change to
> bpf_user_ringbuf_drain() callbacks was missed.
>
> [...]
Here is the summary with links:
- [1/2] bpf: Allow bpf_user_ringbuf_drain() callbacks to return 1
https://git.kernel.org/bpf/bpf/c/c92a7a522438
- [2/2] selftests/bpf: Make bpf_user_ringbuf_drain() selftest callback return 1
https://git.kernel.org/bpf/bpf/c/6e44b9f375a3
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists