aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorQuentin Monnet <[email protected]>2021-07-29 17:20:21 +0100
committerAndrii Nakryiko <[email protected]>2021-07-29 17:03:41 -0700
commit6d2d73cdd673d493f9f3751188757129b1d23fb7 (patch)
tree69aeb245d7b61958200d0e678bdcb56136cd4c0f /tools/perf/scripts/python/export-to-postgresql.py
parentd36216429ff3e69db4f6ea5e0c86b80010f5f30b (diff)
libbpf: Return non-null error on failures in libbpf_find_prog_btf_id()
Variable "err" is initialised to -EINVAL so that this error code is returned when something goes wrong in libbpf_find_prog_btf_id(). However, a recent change in the function made use of the variable in such a way that it is set to 0 if retrieving linear information on the program is successful, and this 0 value remains if we error out on failures at later stages. Let's fix this by setting err to -EINVAL later in the function. Fixes: e9fc3ce99b34 ("libbpf: Streamline error reporting for high-level APIs") Signed-off-by: Quentin Monnet <[email protected]> Signed-off-by: Andrii Nakryiko <[email protected]> Link: https://lore.kernel.org/bpf/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions