From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: Grzegorz Halat <ghalat@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org, linux-doc@vger.kernel.org,
ssaner@redhat.com, atomlin@redhat.com, oleksandr@redhat.com,
vbendel@redhat.com, kirill@shutemov.name,
khlebnikov@yandex-team.ru, borntraeger@de.ibm.com,
Andrew Morton <akpm@linux-foundation.org>,
Iurii Zaikin <yzaikin@google.com>,
Kees Cook <keescook@chromium.org>,
Luis Chamberlain <mcgrof@kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH 1/1] mm: sysctl: add panic_on_mm_error sysctl
Date: Mon, 27 Jan 2020 19:42:56 +0900 [thread overview]
Message-ID: <063e702f-dc5f-b0ca-fe26-508a9f1e8e9a@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <20200127101100.92588-1-ghalat@redhat.com>
On 2020/01/27 19:11, Grzegorz Halat wrote:
> diff --git a/Documentation/admin-guide/sysctl/kernel.rst b/Documentation/admin-guide/sysctl/kernel.rst
> index def074807cee..2fecd6b2547e 100644
> --- a/Documentation/admin-guide/sysctl/kernel.rst
> +++ b/Documentation/admin-guide/sysctl/kernel.rst
> @@ -61,6 +61,7 @@ show up in /proc/sys/kernel:
> - overflowgid
> - overflowuid
> - panic
> +- panic_on_mm_error
Maybe panic_on_inconsistent_mm is better, for an MM error sounds too generic
(e.g. is page allocation failure an error, is OOM killer an error,
is NULL pointer dereference an error, is use-after-free access an error) ?
Also, should this be in /proc/sys/vm/ than /proc/sys/kernel/ ?
> - panic_on_oops
> - panic_on_stackoverflow
> - panic_on_unrecovered_nmi
next prev parent reply other threads:[~2020-01-27 10:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 10:11 [PATCH 1/1] mm: sysctl: add panic_on_mm_error sysctl Grzegorz Halat
2020-01-27 10:28 ` Oleksandr Natalenko
2020-01-27 10:30 ` Aaron Tomlin
2020-01-27 10:42 ` Tetsuo Handa [this message]
2020-01-27 10:55 ` Aaron Tomlin
2020-01-27 11:32 ` Grzegorz Halat
2020-01-27 12:26 ` Qian Cai
2020-01-27 12:51 ` Konstantin Khlebnikov
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=063e702f-dc5f-b0ca-fe26-508a9f1e8e9a@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=akpm@linux-foundation.org \
--cc=atomlin@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=corbet@lwn.net \
--cc=ghalat@redhat.com \
--cc=keescook@chromium.org \
--cc=khlebnikov@yandex-team.ru \
--cc=kirill@shutemov.name \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mcgrof@kernel.org \
--cc=oleksandr@redhat.com \
--cc=ssaner@redhat.com \
--cc=vbendel@redhat.com \
--cc=yzaikin@google.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;
as well as URLs for NNTP newsgroup(s).