diff options
author | Michal Rostecki <mrostecki@opensuse.org> | 2019-05-29 21:31:09 +0300 |
---|---|---|
committer | Alexei Starovoitov <ast@kernel.org> | 2019-06-01 03:03:39 +0300 |
commit | cfd4921049269ee6765b4a1cb820b95d0df5dda5 (patch) | |
tree | 7c5a15cd500f3fd35f8357672f97fd0ab8b0e74e /arch/riscv/net | |
parent | 5fac1718e706d94a7078addee9075cfaea00ca8c (diff) | |
download | linux-cfd4921049269ee6765b4a1cb820b95d0df5dda5.tar.xz |
libbpf: Return btf_fd for load_sk_storage_btf
Before this change, function load_sk_storage_btf expected that
libbpf__probe_raw_btf was returning a BTF descriptor, but in fact it was
returning an information about whether the probe was successful (0 or
1). load_sk_storage_btf was using that value as an argument of the close
function, which was resulting in closing stdout and thus terminating the
process which called that function.
That bug was visible in bpftool. `bpftool feature` subcommand was always
exiting too early (because of closed stdout) and it didn't display all
requested probes. `bpftool -j feature` or `bpftool -p feature` were not
returning a valid json object.
This change renames the libbpf__probe_raw_btf function to
libbpf__load_raw_btf, which now returns a BTF descriptor, as expected in
load_sk_storage_btf.
v2:
- Fix typo in the commit message.
v3:
- Simplify BTF descriptor handling in bpf_object__probe_btf_* functions.
- Rename libbpf__probe_raw_btf function to libbpf__load_raw_btf and
return a BTF descriptor.
v4:
- Fix typo in the commit message.
Fixes: d7c4b3980c18 ("libbpf: detect supported kernel BTF features and sanitize BTF")
Signed-off-by: Michal Rostecki <mrostecki@opensuse.org>
Acked-by: Andrii Nakryiko <andriin@fb.com>
Acked-by: Song Liu <songliubraving@fb.com>
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'arch/riscv/net')
0 files changed, 0 insertions, 0 deletions