summaryrefslogtreecommitdiff
path: root/tools/lib/bpf/libbpf.c
diff options
context:
space:
mode:
authorJiri Olsa <jolsa@kernel.org>2024-11-07 10:43:37 +0100
committerAndrii Nakryiko <andrii@kernel.org>2024-11-11 08:17:54 -0800
commitdcf04676f347133a0c5944152e8d5110aa28d2dd (patch)
tree07a6e95ebe402115e542ed291e58e361cccc480b /tools/lib/bpf/libbpf.c
parent5249b164e666cbdea970c88f2f0e5b06577f9e7b (diff)
downloadlinux-dcf04676f347133a0c5944152e8d5110aa28d2dd.tar.gz
linux-dcf04676f347133a0c5944152e8d5110aa28d2dd.tar.bz2
linux-dcf04676f347133a0c5944152e8d5110aa28d2dd.zip
selftests/bpf: Fix uprobe consumer test (again)
The new uprobe changes bring some new behaviour that we need to reflect in the consumer test. Now pending uprobe instance in the kernel can survive longer and thus might call uretprobe consumer callbacks in some situations in which, previously, such callback would be omitted. We now need to take that into account in uprobe-multi consumer tests. The idea being that uretprobe under test either stayed from before to after (uret_stays + test_bit) or uretprobe instance survived and we have uretprobe active in after (uret_survives + test_bit). uret_survives just states that uretprobe survives if there are *any* uretprobes both before and after (overlapping or not, doesn't matter) and uprobe was attached before. Suggested-by: Andrii Nakryiko <andrii@kernel.org> Signed-off-by: Jiri Olsa <jolsa@kernel.org> Signed-off-by: Andrii Nakryiko <andrii@kernel.org> Link: https://lore.kernel.org/bpf/20241107094337.3848210-1-jolsa@kernel.org
Diffstat (limited to 'tools/lib/bpf/libbpf.c')
0 files changed, 0 insertions, 0 deletions