[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKbGCsfyiLfvwi1iYuTu2Gg5=TXQwUQ3iv73PdNvY8o_NZJ7aQ@mail.gmail.com>
Date: Mon, 27 Jan 2020 12:32:48 +0100
From: Grzegorz Halat <ghalat@...hat.com>
To: Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
Aaron Tomlin <atomlin@...hat.com>
Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org,
linux-fsdevel@...r.kernel.org, linux-doc@...r.kernel.org,
Stan Saner <ssaner@...hat.com>,
Oleksandr Natalenko <oleksandr@...hat.com>,
Vratislav Bendel <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 Mon, 27 Jan 2020 at 11:43, Tetsuo Handa wrote:
>
> 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) ?
>
yes, panic_on_inconsistent_mm is better
> Also, should this be in /proc/sys/vm/ than /proc/sys/kernel/ ?
Agreed
I will wait a day or two for more feedback and send V2 with sysctl
named as 'vm.panic_on_inconsistent_mm'.
Thanks,
--
Grzegorz Halat
Powered by blists - more mailing lists