From: Greg KH <gregkh@linuxfoundation.org>
To: Jani Nikula <jani.nikula@intel.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 4/4] kernel/panic: add verbose logging of kernel taints in backtraces
Date: Tue, 4 Jun 2024 17:34:18 +0200 [thread overview]
Message-ID: <2024060413-seldom-happening-4361@gregkh> (raw)
In-Reply-To: <7321e306166cb2ca2807ab8639e665baa2462e9c.1717146197.git.jani.nikula@intel.com>
On Fri, May 31, 2024 at 12:04:57PM +0300, Jani Nikula wrote:
> With nearly 20 taint flags and respective characters, it's getting a bit
> difficult to remember what each taint flag character means. Add verbose
> logging of the set taints in the format:
>
> Tainted: [P]=PROPRIETARY_MODULE, [W]=WARN
>
> in dump_stack_print_info() when there are taints.
>
> Note that the "negative flag" G is not included.
>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Greg KH <gregkh@linuxfoundation.org>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
prev parent reply other threads:[~2024-06-04 15:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 9:04 [PATCH 0/4] kernel/panic: add more descriptive logging of kernel taints Jani Nikula
2024-05-31 9:04 ` [PATCH 1/4] kernel/panic: return early from print_tainted() when not tainted Jani Nikula
2024-06-04 15:33 ` Greg KH
2024-05-31 9:04 ` [PATCH 2/4] kernel/panic: convert print_tainted() to use struct seq_buf internally Jani Nikula
2024-06-04 15:34 ` Greg KH
2024-05-31 9:04 ` [PATCH 3/4] kernel/panic: initialize taint_flags[] using a macro Jani Nikula
2024-06-04 15:34 ` Greg KH
2024-05-31 9:04 ` [PATCH 4/4] kernel/panic: add verbose logging of kernel taints in backtraces Jani Nikula
2024-06-04 15:34 ` Greg KH [this message]
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=2024060413-seldom-happening-4361@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=jani.nikula@intel.com \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.