linux-kernel - Re: [PATCH 4/4] kernel/panic: add verbose logging of kernel taints in backtraces

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date: Tue, 4 Jun 2024 17:34:18 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Jani Nikula <jani.nikula@...el.com>
Cc: linux-kernel@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 4/4] kernel/panic: add verbose logging of kernel taints
 in backtraces

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@...ux-foundation.org>
> Cc: Greg KH <gregkh@...uxfoundation.org>
> Signed-off-by: Jani Nikula <jani.nikula@...el.com>
> ---

Reviewed-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>