From: Vincent Whitchurch <vincent.whitchurch@axis.com>
To: Kees Cook <keescook@chromium.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Luis R. Rodriguez" <mcgrof@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sysctl: Add panic-fatal-signals
Date: Thu, 17 Jan 2019 11:59:04 +0100 [thread overview]
Message-ID: <20190117105903.dilzmdlqtyiogpo3@axis.com> (raw)
In-Reply-To: <CAGXu5j+dM867PJKR+eHjhUjZvsih5ndHmGJY3y+yWGMf2-gg4w@mail.gmail.com>
On Wed, Jan 16, 2019 at 09:06:18AM -0800, Kees Cook wrote:
> On Wed, Jan 16, 2019 at 4:54 AM Vincent Whitchurch
> <vincent.whitchurch@axis.com> wrote:
> > Add a sysctl which asks the kernel to panic when any userspace process
> > receives a fatal signal which would trigger a core dump. This has
> > proven to be quite useful when debugging problems seen during testing of
> > embedded systems: When combined with kernel core dumps (saved due to
> > the panic), it allows easier debugging of crashes which have their
> > origin in system-wide problems such as buggy drivers or other kernel or
> > hardware-related issues.
> >
> > The crashing process's core dump can be extracted from the kernel core
> > dump using tools such as the crash utility's gcore extension.
>
> Whoa. That's intense. :)
"Insane" is the word I used myself in an earlier draft of the commit
message. :)
> If you have a use-case for it, then I guess I
> can't complain. Given that this is an instant DoS for a system that
> isn't expecting it, I do wonder if it should live behind a CONFIG or
> something to make it available only when really wanted?
Sure, I can put it behind a "depends on EXPERT" config option. Distros
and the like should have no reason to provide access to such a sysctl.
prev parent reply other threads:[~2019-01-17 10:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 12:54 Vincent Whitchurch
2019-01-16 17:06 ` Kees Cook
2019-01-17 10:59 ` Vincent Whitchurch [this message]
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=20190117105903.dilzmdlqtyiogpo3@axis.com \
--to=vincent.whitchurch@axis.com \
--cc=akpm@linux-foundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@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
all inboxes | Powered by JetHome®