[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <60e5c03f-ab34-8095-e2f3-e0ee6a1fb9c1@infradead.org>
Date: Wed, 6 May 2020 17:20:16 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Rafael Aquini <aquini@...hat.com>, linux-kernel@...r.kernel.org
Cc: linux-doc@...r.kernel.org, kexec@...ts.infradead.org,
linux-fsdevel@...r.kernel.org, dyoung@...hat.com, bhe@...hat.com,
corbet@....net, mcgrof@...nel.org, keescook@...omium.org,
akpm@...ux-foundation.org, cai@....pw
Subject: Re: [PATCH] kernel: add panic_on_taint
On 5/6/20 3:28 PM, Rafael Aquini wrote:
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index 7bc83f3d9bdf..75c02c1841b2 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -3404,6 +3404,9 @@
> panic_on_warn panic() instead of WARN(). Useful to cause kdump
> on a WARN().
>
> + panic_on_taint panic() when the kernel gets tainted, if the taint
> + flag being set matches with the assigned bitmask.
> +
Where is the bitmask assigned?
I.e., maybe this text should be more like:
panic_on_taint=<bitmask>
and then the bits are explained. See e.g. panic= and panic_print=
in this same file.
> crash_kexec_post_notifiers
> Run kdump after running panic-notifiers and dumping
> kmsg. This only for the users who doubt kdump always
--
~Randy
Powered by blists - more mailing lists