[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220511153616.9298d246adb1c7fea9ab453b@linux-foundation.org>
Date: Wed, 11 May 2022 15:36:16 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Eddie James <eajames@...ux.ibm.com>
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mm: Add config option for default panic_on_oom value
On Wed, 11 May 2022 17:06:35 -0500 Eddie James <eajames@...ux.ibm.com> wrote:
>
> On 5/11/22 16:56, Andrew Morton wrote:
> > On Wed, 11 May 2022 13:34:00 -0500 Eddie James <eajames@...ux.ibm.com> wrote:
> >
> >> Add the option to kconfig and set the default panic_on_value.
> > Why? What are the use-cases and how does this benefit our users?
>
> If a distribution (for example some embedded system distribution) wants
> the system to always panic when OOM, they may as well configure their
> kernel to do it by default, rather than writing to
> /proc/sys/vm/panic_on_oom every boot. Maybe I'm missing another way to
> do what I want here?
Presumably such a distribution would do this in initramfs initscripts
and forget about it.
What inspired the patch? Have you seen a situation which was best
solved with this change?
Powered by blists - more mailing lists