linux-kernel - Aborting a core dump on a fatal signal

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:   Mon, 25 Sep 2017 04:10:17 -0700
From:   Raymond Jennings <shentino@...il.com>
To:     linux-kernel@...r.kernel.org
Subject: Aborting a core dump on a fatal signal

Would there be any benefit to allowing an in-progress core dump to be
aborted if the dumping process receives a fatal signal?

Example:

Process segfaults, starts dumping core, but it has a lot of virtual
memory allocated so it promptly leads to a queue-clogging deluge of I/O
that takes in some cases several minutes to finish.

In between the time where it snags the crash signal and the time when
it finishes dumping and terminates, I'd like to be able to send it a
SIGKILL or something to abort the core dump.