summaryrefslogtreecommitdiff
path: root/scripts/bpf_doc.py
diff options
context:
space:
mode:
authorIhor Solodrai <ihor.solodrai@pm.me>2024-09-18 22:33:22 +0300
committerAlexei Starovoitov <ast@kernel.org>2024-10-04 03:47:35 +0300
commit8b334d91834666dbc4c1c0b0abed3f855ed16cf3 (patch)
tree62828a1b4e926dabd4ede775a9a6818b5195d6a6 /scripts/bpf_doc.py
parenta1ec23b947538520b3182c598dc2bb9930d032b1 (diff)
downloadlinux-8b334d91834666dbc4c1c0b0abed3f855ed16cf3.tar.xz
libbpf: Change log level of BTF loading error message
Reduce log level of BTF loading error to INFO if BTF is not required. Andrii says: Nowadays the expectation is that the BPF program will have a valid .BTF section, so even though .BTF is "optional", I think it's fine to emit a warning for that case (any reasonably recent Clang will produce valid BTF). Ihor's patch is fixing the situation with an outdated host kernel that doesn't understand BTF. libbpf will try to "upload" the program's BTF, but if that fails and the BPF object doesn't use any features that require having BTF uploaded, then it's just an information message to the user, but otherwise can be ignored. Suggested-by: Andrii Nakryiko <andrii@kernel.org> Signed-off-by: Ihor Solodrai <ihor.solodrai@pm.me> Acked-by: Andrii Nakryiko <andrii@kernel.org> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net> Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'scripts/bpf_doc.py')
0 files changed, 0 insertions, 0 deletions