]> git.karo-electronics.de Git - karo-tx-linux.git/commit
coredump: abort core dump piping only due to a fatal signal
authorBen Chan <benchan@chromium.org>
Wed, 20 Feb 2013 02:15:59 +0000 (13:15 +1100)
committerStephen Rothwell <sfr@canb.auug.org.au>
Wed, 20 Feb 2013 05:53:37 +0000 (16:53 +1100)
commit57cab90c02532603a9ba0f2a87284b718cfd4100
treefd2defe0f0d836cd66f82ee132de4ed371c7c015
parent4cd68d88d475276019ec323f00eb116f8e692472
coredump: abort core dump piping only due to a fatal signal

Make wait_for_dump_helpers() not abort piping the core dump data when the
crashing process has received a non-fatal signal.  The abort still occurs
in the case of SIGKILL.

The rationale is that a crashing process may still receive uninteresting
signals such as SIGCHLD when its core dump data is being redirected to a
helper application.  While it's necessary to allow terminating the core
dump piping via SIGKILL, it's practically more useful for the purpose of
debugging and crash reporting if the core dump piping is not aborted due
to other non-fatal signals.

Signed-off-by: Ben Chan <benchan@chromium.org>
Signed-off-by: Mandeep Singh Baines <msb@chromium.org>
Cc: Oleg Nesterov <oleg@redhat.com>
Cc: Tejun Heo <tj@kernel.org>
Cc: Rafael J. Wysocki <rjw@sisk.pl>
Cc: Ingo Molnar <mingo@redhat.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
fs/coredump.c