From: Randy Dunlap <rdunlap@infradead.org>
To: Rafael Aquini <aquini@redhat.com>, linux-kernel@vger.kernel.org
Cc: linux-doc@vger.kernel.org, kexec@lists.infradead.org,
linux-fsdevel@vger.kernel.org, dyoung@redhat.com, bhe@redhat.com,
corbet@lwn.net, mcgrof@kernel.org, keescook@chromium.org,
akpm@linux-foundation.org, cai@lca.pw
Subject: Re: [PATCH] kernel: add panic_on_taint
Date: Wed, 6 May 2020 17:20:16 -0700 [thread overview]
Message-ID: <60e5c03f-ab34-8095-e2f3-e0ee6a1fb9c1@infradead.org> (raw)
In-Reply-To: <20200506222815.274570-1-aquini@redhat.com>
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
next prev parent reply other threads:[~2020-05-07 0:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 22:28 [PATCH] kernel: add panic_on_taint Rafael Aquini
2020-05-06 23:24 ` Luis Chamberlain
2020-05-07 0:12 ` Rafael Aquini
2020-05-07 0:20 ` Randy Dunlap [this message]
2020-05-07 2:50 ` Qian Cai
2020-05-07 20:42 ` Rafael Aquini
2020-05-07 22:05 ` Qian Cai
2020-05-07 22:15 ` Rafael Aquini
2020-05-07 23:07 ` Qian Cai
2020-05-07 23:36 ` Rafael Aquini
2020-05-08 0:28 ` Qian Cai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=60e5c03f-ab34-8095-e2f3-e0ee6a1fb9c1@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=aquini@redhat.com \
--cc=bhe@redhat.com \
--cc=cai@lca.pw \
--cc=corbet@lwn.net \
--cc=dyoung@redhat.com \
--cc=keescook@chromium.org \
--cc=kexec@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).