linux-kernel - Re: [PATCH] Documentation: Add detailed explanation for 'N' taint flag

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]

Message-ID: <87jzh398jk.fsf@trenco.lwn.net>
Date: Mon, 29 Jul 2024 15:45:35 -0600
From: Jonathan Corbet <corbet@....net>
To: Benjamin Poirier <bpoirier@...dia.com>
Cc: Thorsten Blum <thorsten.blum@...lux.com>, Luis Chamberlain
 <mcgrof@...nel.org>, David Gow <davidgow@...gle.com>, Shuah Khan
 <skhan@...uxfoundation.org>, Brendan Higgins <brendan.higgins@...ux.dev>,
 linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Documentation: Add detailed explanation for 'N' taint flag

Benjamin Poirier <bpoirier@...dia.com> writes:

> Every taint flag has an entry in the "More detailed explanation" section
> except for the 'N' flag. That omission was probably just an oversight so
> add an entry for that flag.
>
> Fixes: 2852ca7fba9f ("panic: Taint kernel if tests are run")
> Signed-off-by: Benjamin Poirier <bpoirier@...dia.com>
> ---
>  Documentation/admin-guide/tainted-kernels.rst | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/admin-guide/tainted-kernels.rst b/Documentation/admin-guide/tainted-kernels.rst
> index f92551539e8a..700aa72eecb1 100644
> --- a/Documentation/admin-guide/tainted-kernels.rst
> +++ b/Documentation/admin-guide/tainted-kernels.rst
> @@ -182,3 +182,5 @@ More detailed explanation for tainting
>       produce extremely unusual kernel structure layouts (even performance
>       pathological ones), which is important to know when debugging. Set at
>       build time.
> +
> + 18) ``N`` if an in-kernel test, such as a KUnit test, has been run.

Applied, thanks.

jon