linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Thorsten Leemhuis <linux@leemhuis.info>, linux-kernel@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>, linux-doc@vger.kernel.org
Subject: Re: [PATCH] kernel-chktaint: add reporting for tainted modules
Date: Tue, 28 Oct 2025 12:51:44 -0700	[thread overview]
Message-ID: <892775bd-401d-46df-a730-a4f9a09f5149@infradead.org> (raw)
In-Reply-To: <a842c1c1-948c-40bd-b564-9b746be69cd2@leemhuis.info>



On 10/28/25 3:05 AM, Thorsten Leemhuis wrote:
> On 10/28/25 08:12, Randy Dunlap wrote:
>> Check all loaded modules and report any that have their 'taint'
>> flags set along with a count of all tainted modules.
>> The tainted module output format is:
>> <module_name>: taint=<flags>
>>
>> Example output:
>>
>> Kernel is "tainted" for the following reasons:
>>  * externally-built ('out-of-tree') module was loaded  (#12)
>>  * unsigned module was loaded (#13)
>> Raw taint value as int/string: 12288/'G           OE      '
> 
> I wonder if it would be easier more readable if the format used above...
>> Modules tainted: count=1
>> dump_test: taint=OE
> 
> ...would be reused here somewhat. Like this maybe?
> 
> Modules tainted: 1
>  * dump_test (OE)

Yeah, I like that. Thanks.

-- 
~Randy


      reply	other threads:[~2025-10-28 19:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-28  7:12 [PATCH] kernel-chktaint: add reporting for tainted modules Randy Dunlap
2025-10-28 10:05 ` Thorsten Leemhuis
2025-10-28 19:51   ` Randy Dunlap [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=892775bd-401d-46df-a730-a4f9a09f5149@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@leemhuis.info \
    /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).