diff options
author | Eric W. Biederman <ebiederm@xmission.com> | 2019-05-16 10:55:21 -0500 |
---|---|---|
committer | Eric W. Biederman <ebiederm@xmission.com> | 2019-05-27 09:36:27 -0500 |
commit | 82e10af2248d2d09c99834613f1b47d5002dc379 (patch) | |
tree | 4a60fcac51f5cb91957465aea4726dfad68ef6f8 /drivers | |
parent | 7a0cf094944e2540758b7f957eb6846d5126f535 (diff) | |
download | linux-82e10af2248d2d09c99834613f1b47d5002dc379.tar.gz linux-82e10af2248d2d09c99834613f1b47d5002dc379.tar.bz2 linux-82e10af2248d2d09c99834613f1b47d5002dc379.zip |
signal/arm64: Use force_sig not force_sig_fault for SIGKILL
I don't think this is userspace visible but SIGKILL does not have
any si_codes that use the fault member of the siginfo union. Correct
this the simple way and call force_sig instead of force_sig_fault when
the signal is SIGKILL.
The two know places where synchronous SIGKILL are generated are
do_bad_area and fpsimd_save. The call paths to force_sig_fault are:
do_bad_area
arm64_force_sig_fault
force_sig_fault
force_signal_inject
arm64_notify_die
arm64_force_sig_fault
force_sig_fault
Which means correcting this in arm64_force_sig_fault is enough
to ensure the arm64 code is not misusing the generic code, which
could lead to maintenance problems later.
Cc: stable@vger.kernel.org
Cc: Dave Martin <Dave.Martin@arm.com>
Cc: James Morse <james.morse@arm.com>
Cc: Will Deacon <will.deacon@arm.com>
Acked-by: Will Deacon <will.deacon@arm.com>
Fixes: af40ff687bc9 ("arm64: signal: Ensure si_code is valid for all fault signals")
Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions