diff options
author | Athira Rajeev <[email protected]> | 2023-01-05 17:47:41 +0530 |
---|---|---|
committer | Arnaldo Carvalho de Melo <[email protected]> | 2023-02-06 15:00:05 -0300 |
commit | 67ef66bad42b32237a0ddc6bdb5cc2653c354fec (patch) | |
tree | 89b0c835cef59561273ec7392b7bf4161b107f64 /lib/test_fortify/write_overflow-strncpy-src.c | |
parent | 4e846311a9be53999d9c52bba4ce76939d2b0e64 (diff) |
perf probe: Update the exit error codes in function try_to_find_probe_trace_event
try_to_find_probe_trace_events() uses return error code as ENOENT in two
places.
First place is after open_debuginfo() when opening debuginfo fails and
secondly, after when not finding the probe point.
This function is invoked during BPF load and there are other exit points
in this code path which returns ENOENT. This makes it difficult to
understand the exact reason for exit.
Patches changes the exit code from ENOENT to:
- ENODATA when it fails to find debuginfo
- ENODEV when it fails to find probe point
Signed-off-by: Athira Rajeev <[email protected]>
Cc: Andi Kleen <[email protected]>
Cc: Disha Goel <[email protected]>
Cc: Ian Rogers <[email protected]>
Cc: James Clark <[email protected]>
Cc: Jiri Olsa <[email protected]>
Cc: Kajol Jain <[email protected]>
Cc: Madhavan Srinivasan <[email protected]>
Cc: Michael Ellerman <[email protected]>
Cc: Nageswara R Sastry <[email protected]>
Cc: Namhyung Kim <[email protected]>
Cc: [email protected]
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Arnaldo Carvalho de Melo <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy-src.c')
0 files changed, 0 insertions, 0 deletions