From: Luis Chamberlain <mcgrof@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Vincent Whitchurch <vincent.whitchurch@axis.com>,
keescook@chromium.org, linux-kernel@vger.kernel.org,
Vincent Whitchurch <rabinv@axis.com>
Subject: Re: [PATCH v2] sysctl: Add panic-fatal-signals
Date: Wed, 30 Jan 2019 06:48:51 -0800 [thread overview]
Message-ID: <20190130144851.GK11489@garbanzo.do-not-panic.com> (raw)
In-Reply-To: <20190128100545.b62193aa8f49e1de8d6ea8b7@linux-foundation.org>
On Mon, Jan 28, 2019 at 10:05:45AM -0800, Andrew Morton wrote:
> On Mon, 28 Jan 2019 09:49:59 +0100 Vincent Whitchurch <vincent.whitchurch@axis.com> wrote:
> > --- a/init/Kconfig
> > +++ b/init/Kconfig
> > @@ -1242,6 +1242,20 @@ config SYSCTL_SYSCALL
> >
> > If unsure say N here.
> >
> > +config SYSCTL_PANIC_FATAL_SIGNALS
> > + bool "panic-fatal-signals sysctl" if EXPERT
> > + depends on PROC_SYSCTL
> > + help
> > + If you say Y here, a kernel.panic-fatal-signals sysctl will be
> > + offered. If this sysctl is turned on, the kernel will panic if any
> > + userspace process receives a fatal signal which would trigger a core
> > + dump.
> > +
> > + When used together with kernel core dumps, this can be useful for
> > + debugging some system-wide problems, primarily on embedded systems.
> > +
> > + If unsure, say N.
>
> I suggest that the Kconfig help and the forthcoming documentation
> should clearly explain the dangers of enabling this!
And so, should default to n.
Luis
next prev parent reply other threads:[~2019-01-30 14:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 8:49 Vincent Whitchurch
2019-01-28 18:05 ` Andrew Morton
2019-01-30 14:48 ` Luis Chamberlain [this message]
2019-01-30 15:02 ` Richard Weinberger
2019-01-30 16:29 ` Vincent Whitchurch
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=20190130144851.GK11489@garbanzo.do-not-panic.com \
--to=mcgrof@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rabinv@axis.com \
--cc=vincent.whitchurch@axis.com \
/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
Powered by JetHome