diff options
| author |   Andrii Nakryiko <andrii@kernel.org> | 2024-11-11 20:14:57 -0800 |
|---|---|---|
| committer | Andrii Nakryiko <andrii@kernel.org> | 2024-11-11 20:29:46 -0800 |
| commit | 47e2c45c9c89fe71893aa234dc1a27dec1c7c8d2 (patch) | |
| tree | b4b70b0c4561728a2b9d8bfcdcaed6d096873ca2 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | bpf: Replace the document for PTR_TO_BTF_ID_OR_NULL (diff) | |
| parent | libbpf: Stringify errno in log messages in the remaining code (diff) | |
| download | wireguard-linux-47e2c45c9c89fe71893aa234dc1a27dec1c7c8d2.tar.xz wireguard-linux-47e2c45c9c89fe71893aa234dc1a27dec1c7c8d2.zip | |
Merge branch 'libbpf-stringify-error-codes-in-log-messages'
Mykyta Yatsenko says:
====================
libbpf: stringify error codes in log messages
From: Mykyta Yatsenko <yatsenko@meta.com>
Libbpf may report error in 2 ways:
1. Numeric errno
2. Errno's text representation, returned by strerror
Both ways may be confusing for users: numeric code requires people to
know how to find its meaning and strerror may be too generic and
unclear.
These patches modify libbpf error reporting by swapping numeric codes
and strerror with the standard short error name, for example:
"failed to attach: -22" becomes "failed to attach: -EINVAL".
====================
Link: https://patch.msgid.link/20241111212919.368971-1-mykyta.yatsenko5@gmail.com
Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions