summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/syscall-counts.py
diff options
context:
space:
mode:
authorAndrii Nakryiko <andrii@kernel.org>2024-05-06 17:13:32 -0700
committerMartin KaFai Lau <martin.lau@kernel.org>2024-05-07 16:21:59 -0700
commit548c2ede0dc81cb8c86f3a72c1c63fe1c179cbfe (patch)
tree7b7d7cdb28f3dd005ebaeb22fc423a70a25edfb0 /tools/perf/scripts/python/syscall-counts.py
parent9d66d60e968d85742569d025a2fb509cb57333bb (diff)
libbpf: fix libbpf_strerror_r() handling unknown errors
strerror_r(), used from libbpf-specific libbpf_strerror_r() wrapper is documented to return error in two different ways, depending on glibc version. Take that into account when handling strerror_r()'s own errors, which happens when we pass some non-standard (internal) kernel error to it. Before this patch we'd have "ERROR: strerror_r(524)=22", which is quite confusing. Now for the same situation we'll see a bit less visually scary "unknown error (-524)". At least we won't confuse user with irrelevant EINVAL (22). Signed-off-by: Andrii Nakryiko <andrii@kernel.org> Link: https://lore.kernel.org/r/20240507001335.1445325-5-andrii@kernel.org Signed-off-by: Martin KaFai Lau <martin.lau@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts.py')
0 files changed, 0 insertions, 0 deletions