linux-kernel - Re: [PATCH] kernel/watchdog.c: convert {soft/hard}lockup boot parameters to sysctl aliases

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]

Date:   Thu, 7 May 2020 16:06:18 -0700
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     "Guilherme G. Piccoli" <gpiccoli@...onical.com>
Cc:     linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
        keescook@...omium.org, yzaikin@...gle.com, mcgrof@...nel.org,
        vbabka@...e.cz, kernel@...ccoli.net
Subject: Re: [PATCH] kernel/watchdog.c: convert {soft/hard}lockup boot
 parameters to sysctl aliases

On Thu,  7 May 2020 18:46:24 -0300 "Guilherme G. Piccoli" <gpiccoli@...onical.com> wrote:

> After a recent change introduced by Vlastimil's series [0], kernel is
> able now to handle sysctl parameters on kernel command line; also, the
> series introduced a simple infrastructure to convert legacy boot
> parameters (that duplicate sysctls) into sysctl aliases.
> 
> This patch converts the watchdog parameters softlockup_panic and
> {hard,soft}lockup_all_cpu_backtrace to use the new alias infrastructure.
> It fixes the documentation too, since the alias only accepts values 0
> or 1, not the full range of integers. We also took the opportunity here
> to improve the documentation of the previously converted hung_task_panic
> (see the patch series [0]) and put the alias table in alphabetical order.

We have a lot of sysctls.  What is the motivation for converting these
particular ones?