Thread (1 message) 1 message, 1 author, 2021-10-21

Re: [PATCH 21/20] signal: Replace force_sigsegv(SIGSEGV) with force_fatal_sig(SIGSEGV)

From: Eric W. Biederman <hidden>
Date: 2021-10-21 13:34:32
Also in: linux-arch, linux-mips, linux-s390, linux-sh, lkml, sparclinux

Geert Uytterhoeven [off-list ref] writes:
Hi Eric,

Patch 21/20?
In reviewing another part of the patchset Linus asked if force_sigsegv
could go away.  It can't completely but I can get this far.

Given that it is just a cleanup it makes most sense to me as an
additional patch on top of what is already here.

On Wed, Oct 20, 2021 at 11:52 PM Eric W. Biederman
[off-list ref] wrote:
quoted
Now that force_fatal_sig exists it is unnecessary and a bit confusing
to use force_sigsegv in cases where the simpler force_fatal_sig is
wanted.  So change every instance we can to make the code clearer.

Signed-off-by: "Eric W. Biederman" <redacted>
quoted
 arch/m68k/kernel/traps.c        | 2 +-
Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
Thank you.

Eric
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help