summaryrefslogtreecommitdiffstats
path: root/tools
diff options
context:
space:
mode:
authorJiri Olsa <jolsa@kernel.org>2023-12-17 22:55:37 +0100
committerAndrii Nakryiko <andrii@kernel.org>2023-12-18 09:51:30 -0800
commit3983c00281d96af2ba611254d679107b5c390627 (patch)
tree61813969a52053d327d24a86eb8dac978853f4a0 /tools
parente58aac1a9a179fa9dab3025ef955cdb548c439f2 (diff)
downloadlinux-stable-3983c00281d96af2ba611254d679107b5c390627.tar.gz
linux-stable-3983c00281d96af2ba611254d679107b5c390627.tar.bz2
linux-stable-3983c00281d96af2ba611254d679107b5c390627.zip
bpf: Fail uprobe multi link with negative offset
Currently the __uprobe_register will return 0 (success) when called with negative offset. The reason is that the call to register_for_each_vma and then build_map_info won't return error for negative offset. They just won't do anything - no matching vma is found so there's no registered breakpoint for the uprobe. I don't think we can change the behaviour of __uprobe_register and fail for negative uprobe offset, because apps might depend on that already. But I think we can still make the change and check for it on bpf multi link syscall level. Also moving the __get_user call and check for the offsets to the top of loop, to fail early without extra __get_user calls for ref_ctr_offset and cookie arrays. Signed-off-by: Jiri Olsa <jolsa@kernel.org> Signed-off-by: Andrii Nakryiko <andrii@kernel.org> Acked-by: Song Liu <song@kernel.org> Link: https://lore.kernel.org/bpf/20231217215538.3361991-2-jolsa@kernel.org
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions