diff options
| author |  Ian Rogers <irogers@google.com>
| 2024-01-25 15:18:40 -0800 |
|---|---|---|
| committer |  Andrii Nakryiko <andrii@kernel.org>
| 2024-01-29 16:42:42 -0800 |
| commit | f2e4040c82d3fddd11fa7c64e8f810e6f9cb7460 (patch) | |
| tree | f413ae5bdb8800f9612a875e827cc811bd3639b9 /tools/lib/vsprintf.c | |
| parent | perf/bpf: Fix duplicate type check (diff) | |
| download | linux-f2e4040c82d3fddd11fa7c64e8f810e6f9cb7460.tar.gz linux-f2e4040c82d3fddd11fa7c64e8f810e6f9cb7460.tar.bz2 linux-f2e4040c82d3fddd11fa7c64e8f810e6f9cb7460.zip | |
libbpf: Add some details for BTF parsing failures
As CONFIG_DEBUG_INFO_BTF is default off the existing "failed to find
valid kernel BTF" message makes diagnosing the kernel build issue somewhat
cryptic. Add a little more detail with the hope of helping users.
Before:
```
libbpf: failed to find valid kernel BTF
libbpf: Error loading vmlinux BTF: -3
```
After not accessible:
```
libbpf: kernel BTF is missing at '/sys/kernel/btf/vmlinux', was CONFIG_DEBUG_INFO_BTF enabled?
libbpf: failed to find valid kernel BTF
libbpf: Error loading vmlinux BTF: -3
```
After not readable:
```
libbpf: failed to read kernel BTF from (/sys/kernel/btf/vmlinux): -1
```
Closes: https://lore.kernel.org/bpf/CAP-5=fU+DN_+Y=Y4gtELUsJxKNDDCOvJzPHvjUVaUoeFAzNnig@mail.gmail.com/
Signed-off-by: Ian Rogers <irogers@google.com>
Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Link: https://lore.kernel.org/bpf/20240125231840.1647951-1-irogers@google.com
Diffstat (limited to 'tools/lib/vsprintf.c')
0 files changed, 0 insertions, 0 deletions