[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <063e702f-dc5f-b0ca-fe26-508a9f1e8e9a@I-love.SAKURA.ne.jp>
Date: Mon, 27 Jan 2020 19:42:56 +0900
From: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
To: Grzegorz Halat <ghalat@...hat.com>
Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org,
linux-fsdevel@...r.kernel.org, linux-doc@...r.kernel.org,
ssaner@...hat.com, atomlin@...hat.com, oleksandr@...hat.com,
vbendel@...hat.com, kirill@...temov.name,
khlebnikov@...dex-team.ru, borntraeger@...ibm.com,
Andrew Morton <akpm@...ux-foundation.org>,
Iurii Zaikin <yzaikin@...gle.com>,
Kees Cook <keescook@...omium.org>,
Luis Chamberlain <mcgrof@...nel.org>,
Jonathan Corbet <corbet@....net>
Subject: Re: [PATCH 1/1] mm: sysctl: add panic_on_mm_error sysctl
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
Powered by blists - more mailing lists