diff options
| author | Eric W. Biederman <[email protected]> | 2021-10-20 12:43:52 -0500 |
|---|---|---|
| committer | Eric W. Biederman <[email protected]> | 2021-10-25 15:56:29 -0500 |
| commit | ce0ee4e6ac99606f3945f4d47775544edc3f7985 (patch) | |
| tree | 1333aa77192bfb29903ddecb2f8774b59380325b /lib/test_fortify/write_overflow-memcpy.c | |
| parent | 95bf9d646c3c3f95cb0be7e703b371db8da5be68 (diff) | |
signal/sh: Use force_sig(SIGKILL) instead of do_group_exit(SIGKILL)
Today the sh code allocates memory the first time a process uses
the fpu. If that memory allocation fails, kill the affected task
with force_sig(SIGKILL) rather than do_group_exit(SIGKILL).
Calling do_group_exit from an exception handler can potentially lead
to dead locks as do_group_exit is not designed to be called from
interrupt context. Instead use force_sig(SIGKILL) to kill the
userspace process. Sending signals in general and force_sig in
particular has been tested from interrupt context so there should be
no problems.
Cc: Yoshinori Sato <[email protected]>
Cc: Rich Felker <[email protected]>
Cc: [email protected]
Fixes: 0ea820cf9bf5 ("sh: Move over to dynamically allocated FPU context.")
Link: https://lkml.kernel.org/r/[email protected]
Signed-off-by: Eric W. Biederman <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-memcpy.c')
0 files changed, 0 insertions, 0 deletions