[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <9eab7f80-bad4-bcb1-7ec7-b6b90839b13a@suse.cz>
Date: Wed, 25 Mar 2020 10:33:13 +0100
From: Vlastimil Babka <vbabka@...e.cz>
To: Kees Cook <keescook@...omium.org>,
"Guilherme G. Piccoli" <gpiccoli@...onical.com>
Cc: linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-doc@...r.kernel.org, mcgrof@...nel.org, yzaikin@...gle.com,
tglx@...utronix.de, penguin-kernel@...ove.SAKURA.ne.jp,
akpm@...ux-foundation.org, cocci@...teme.lip6.fr,
linux-api@...r.kernel.org, kernel@...ccoli.net,
randy Dunlap <rdunlap@...radead.org>
Subject: Re: [PATCH V2] kernel/hung_task.c: Introduce sysctl to print all
traces when a hung task is detected
On 3/24/20 7:20 PM, Kees Cook wrote:
> On Tue, Mar 24, 2020 at 09:45:40AM -0300, Guilherme G. Piccoli wrote:
>> Thanks Randy and Vlastimil for the comments. I really liked your
>> approach Vlastimil, I agree that we have no reason to not have a generic
>> sysctl setting via cmdline mechanism - I'll rework this patch removing
>> the kernel parameter (same for other patch I just submitted).
>
> I've been thinking we'll likely want to have a big patch series that
> removes all the old "duplicate" boot params and adds some kind of
> "alias" mechanism.
>
> Vlastimil, have you happened to keep a list of other "redundant" boot
> params you've noticed in the kernel? I bet there are a lot. :)
Well, I found about 4 that mentioned sysctl in
Documentation/admin-guide/kernel-parameters.txt
I suspect there will be more, but won't be trivial to identify them.
Powered by blists - more mailing lists