[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <202003241119.A666E1C694@keescook>
Date: Tue, 24 Mar 2020 11:20:55 -0700
From: Kees Cook <keescook@...omium.org>
To: "Guilherme G. Piccoli" <gpiccoli@...onical.com>
Cc: Vlastimil Babka <vbabka@...e.cz>, 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 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. :)
--
Kees Cook
Powered by blists - more mailing lists