diff options
| author | Eric W. Biederman <ebiederm@xmission.com> | 2019-05-23 19:11:19 +0300 |
|---|---|---|
| committer | Will Deacon <will.deacon@arm.com> | 2019-05-29 13:05:25 +0300 |
| commit | d76cac67db40c172791ce07948367b96a758e45b (patch) | |
| tree | 63b43acda8e563e61ea0dfa2d628ca56e38e7fec /net/switchdev/switchdev.c | |
| parent | 3fd00beb14a56c5ca10c3f67e5b8156f4f9223b5 (diff) | |
| download | linux-d76cac67db40c172791ce07948367b96a758e45b.tar.xz | |
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>
Fixes: af40ff687bc9 ("arm64: signal: Ensure si_code is valid for all fault signals")
Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
Diffstat (limited to 'net/switchdev/switchdev.c')
0 files changed, 0 insertions, 0 deletions