aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorAndrii Nakryiko <andrii@kernel.org>2022-10-13 08:27:38 -0700
committerAndrii Nakryiko <andrii@kernel.org>2022-10-13 08:28:12 -0700
commite7b09357453a99e6f9e74c39e9ca1363c22c0b96 (patch)
treebc4231cfacdb6fb9493d576ea718775f325086a0 /tools/perf/scripts/python/export-to-postgresql.py
parentMerge tag 'net-next-6.1' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next (diff)
parentselftests/bpf: Make bpf_user_ringbuf_drain() selftest callback return 1 (diff)
downloadlinux-dev-e7b09357453a99e6f9e74c39e9ca1363c22c0b96.tar.xz
linux-dev-e7b09357453a99e6f9e74c39e9ca1363c22c0b96.zip
Merge branch 'Allow bpf_user_ringbuf_drain() callbacks to return 1'
David Vernet says: ==================== 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. This patch set fixes this oversight, and updates the user_ringbuf selftests to return 1 in a callback to catch future instances of regression. ==================== Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions