lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b597cc79-0f8a-c32d-397e-0c04777e9491@linux.ibm.com>
Date:   Wed, 11 May 2022 17:06:35 -0500
From:   Eddie James <eajames@...ux.ibm.com>
To:     Andrew Morton <akpm@...ux-foundation.org>
Cc:     linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mm: Add config option for default panic_on_oom value


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?


Thanks,

Eddie


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ