diff options
| author | Umang Jain <[email protected]> | 2024-09-18 22:00:57 +0530 |
|---|---|---|
| committer | Greg Kroah-Hartman <[email protected]> | 2024-10-09 11:58:47 +0200 |
| commit | 72925dec88342c50ca3a39c91f6614d6921bb46f (patch) | |
| tree | 7995d1f6d5684ba045ae277c122fedc765e723e8 /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | fbd06c751a5c2092484f6a43fed0120ee8844d6a (diff) | |
staging: vchiq_core: Return -EINTR in queue_message() on interrupt
queue_message() uses mutex_lock_killable() and
wait_for_completion_killable() variations of locking and wait event
completions respectively. These functions return either 0 (on success)
or -EINTR, if interrupted by a fatal signal (as documented in the
kernel).
However, queue_message() is currently returning -EAGAIN if these
killable functions are interrupted by fatal signals. Bubbling up
-EAGAIN might give a sense to the caller, that the code path can
be re-tried however, in actual sense, a fatal signal has been
received by the process and the process is going away.
Hence, we should align the return value with what these killable
versions will return i.e. -EINTR (Interrupted system call).
Signed-off-by: Umang Jain <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions