bpftool: Fix prog dump by tag
Subsystems (4)
Jiri Olsa
reviewerPATCH 1/1 bpftool: Fix prog dump by tag
Lance reported an issue with bpftool not being able to dump program if there are more programs loaded and you want to dump any but the first program, like:
# bpftool prog 28: kprobe name trace_req_start tag 1dfc28ba8b3dd597 gpl loaded_at 2019-01-18T17:02:40+1100 uid 0 xlated 112B jited 109B memlock 4096B map_ids 13 29: kprobe name trace_req_compl tag 5b6a5ecc6030a683 gpl loaded_at 2019-01-18T17:02:40+1100 uid 0 xlated 928B jited 575B memlock 4096B map_ids 13,14 # bpftool prog dum jited tag 1dfc28ba8b3dd597 0: push %rbp 1: mov %rsp,%rbp ...
# bpftool prog dum jited tag 5b6a5ecc6030a683
Error: can't get prog info (29): Bad address
The problem is in the prog_fd_by_tag function not cleaning the struct bpf_prog_info before another request, so the previous program length is still in there and kernel assumes it needs to dump the program, which fails because there's no user pointer set.
Moving the struct bpf_prog_info declaration into the loop, so it gets cleaned before each query.
--- tools/bpf/bpftool/prog.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
tools/bpf/bpftool/prog.c +3 -2
@@ -78,13 +78,14 @@ static void print_boot_time(__u64 nsecs, char *buf, unsigned int size)static int prog_fd_by_tag (unsigned char *tag) { -struct bpf_prog_info info = {}; -__u32 len =sizeof (info);unsigned int id =0 ;int err;int fd;while (true) { +struct bpf_prog_info info = {}; +__u32 len =sizeof (info); + err =bpf_prog_get_next_id (id, &id);if (err) {p_err ("%s" ,strerror (errno));
Signature · 1 line
2.17.2
2019-01-18 13:58 UTC+0100 ~ Jiri Olsa <[email protected]>
Quoted 25 lines
Lance reported an issue with bpftool not being able to dump program if there are more programs loaded and you want to dump any but the first program, like:
# bpftool prog 28: kprobe name trace_req_start tag 1dfc28ba8b3dd597 gpl loaded_at 2019-01-18T17:02:40+1100 uid 0 xlated 112B jited 109B memlock 4096B map_ids 13 29: kprobe name trace_req_compl tag 5b6a5ecc6030a683 gpl loaded_at 2019-01-18T17:02:40+1100 uid 0 xlated 928B jited 575B memlock 4096B map_ids 13,14 # bpftool prog dum jited tag 1dfc28ba8b3dd597 0: push %rbp 1: mov %rsp,%rbp ...# bpftool prog dum jited tag
5b6a5ecc6030a683
Error: can't get prog info (29): Bad addressThe problem is in the
prog_fd_by_tagfunction not cleaning the structbpf_prog_infobefore another request, so the previous program length is still in there and kernel assumes it needs to dump the program, which fails because there's no user pointer set.
Quoted 5 lines
Moving the struct
bpf_prog_infodeclaration into the loop, so it gets cleaned before each query.Reported-by Lance Digby <[email protected]>Signed-off-by Jiri Olsa <[email protected]>
Thanks for the fix!
Quoted 25 lines · Jiri Olsa
Lance reported an issue with bpftool not being able to dump program if there are more programs loaded and you want to dump any but the first program, like:
# bpftool prog 28: kprobe name trace_req_start tag 1dfc28ba8b3dd597 gpl loaded_at 2019-01-18T17:02:40+1100 uid 0 xlated 112B jited 109B memlock 4096B map_ids 13 29: kprobe name trace_req_compl tag 5b6a5ecc6030a683 gpl loaded_at 2019-01-18T17:02:40+1100 uid 0 xlated 928B jited 575B memlock 4096B map_ids 13,14 # bpftool prog dum jited tag 1dfc28ba8b3dd597 0: push %rbp 1: mov %rsp,%rbp ...# bpftool prog dum jited tag
5b6a5ecc6030a683
Error: can't get prog info (29): Bad addressThe problem is in the
prog_fd_by_tagfunction not cleaning the structbpf_prog_infobefore another request, so the previous program length is still in there and kernel assumes it needs to dump the program, which fails because there's no user pointer set.
Quoted 5 lines
Moving the struct
bpf_prog_infodeclaration into the loop, so it gets cleaned before each query.Reported-by Lance Digby <[email protected]>Signed-off-by Jiri Olsa <[email protected]>
Aw.
Thanks!
Quoted 25 lines · Jiri Olsa
Lance reported an issue with bpftool not being able to dump program if there are more programs loaded and you want to dump any but the first program, like:
# bpftool prog 28: kprobe name trace_req_start tag 1dfc28ba8b3dd597 gpl loaded_at 2019-01-18T17:02:40+1100 uid 0 xlated 112B jited 109B memlock 4096B map_ids 13 29: kprobe name trace_req_compl tag 5b6a5ecc6030a683 gpl loaded_at 2019-01-18T17:02:40+1100 uid 0 xlated 928B jited 575B memlock 4096B map_ids 13,14 # bpftool prog dum jited tag 1dfc28ba8b3dd597 0: push %rbp 1: mov %rsp,%rbp ...# bpftool prog dum jited tag
5b6a5ecc6030a683
Error: can't get prog info (29): Bad addressThe problem is in the
prog_fd_by_tagfunction not cleaning the structbpf_prog_infobefore another request, so the previous program length is still in there and kernel assumes it needs to dump the program, which fails because there's no user pointer set.
Quoted 5 lines
Moving the struct
bpf_prog_infodeclaration into the loop, so it gets cleaned before each query.Reported-by Lance Digby <[email protected]>Signed-off-by Jiri Olsa <[email protected]>
Applied to bpf and added Fixes tags, thanks!