summaryrefslogtreecommitdiffstats
path: root/tools/bpf
diff options
context:
space:
mode:
authorAlexei Starovoitov <ast@kernel.org>2018-12-04 08:18:14 -0800
committerAlexei Starovoitov <ast@kernel.org>2018-12-04 08:18:14 -0800
commit2a95471c3397734ba6869ca3fa084490fb35b40b (patch)
tree416ce2a6672f6c97c074df80912ec09e2ff0c29c /tools/bpf
parentd59dd69d5576d699d7d3f5da0b4738c3a36d0133 (diff)
parentdf47fc376df8338fdc9b27a5c9162a08f6e6157c (diff)
downloadlinux-2a95471c3397734ba6869ca3fa084490fb35b40b.tar.bz2
Merge branch 'prog_test_run-improvement'
Lorenz Bauer says: ==================== Right now, there is no safe way to use BPF_PROG_TEST_RUN with data_out. This is because bpf_test_finish copies the output buffer to user space without checking its size. This can lead to the kernel overwriting data in user space after the buffer if xdp_adjust_head and friends are in play. Thanks to everyone for their advice and patience with this patch set! Changes in v5: * Fix up libbpf.map Changes in v4: * Document bpf_prog_test_run and bpf_prog_test_run_xattr * Use struct bpf_prog_test_run_attr for return values Changes in v3: * Introduce bpf_prog_test_run_xattr instead of modifying the existing function Changes in v2: * Make the syscall return ENOSPC if data_size_out is too small * Make bpf_prog_test_run return EINVAL if size_out is missing * Document the new behaviour of data_size_out ==================== Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'tools/bpf')
0 files changed, 0 insertions, 0 deletions