From: Raymond Jennings <shentino@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Aborting a core dump on a fatal signal
Date: Mon, 25 Sep 2017 04:10:17 -0700 [thread overview]
Message-ID: <1506337817.31845.1.camel@gmail.com> (raw)
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.
reply other threads:[~2017-09-25 11:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1506337817.31845.1.camel@gmail.com \
--to=shentino@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox