linux-kernel - Re: [RFC PATCH v2 08/26] docs: reporting-bugs: make readers check the 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 for Android: free password hash cracker in your pocket

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

Message-ID: <90ffa1af-29b1-49d9-a62b-628fc651a761@leemhuis.info>
Date:   Thu, 19 Nov 2020 11:26:04 +0100
From:   Thorsten Leemhuis <linux@...mhuis.info>
To:     Jonathan Corbet <corbet@....net>
Cc:     Randy Dunlap <rdunlap@...radead.org>, linux-doc@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH v2 08/26] docs: reporting-bugs: make readers check the
 taint flag

Am 19.11.20 um 01:05 schrieb Jonathan Corbet:
> On Thu, 12 Nov 2020 18:58:45 +0100
> Thorsten Leemhuis <linux@...mhuis.info> wrote:
> 
>> +If your kernel is tainted, study
>> +:ref:`Documentation/admin-guide/tainted-kernels.rst <taintedkernels>` to find
>> +out why. Try to eliminate the reason. Often it's caused by one these three
>> +things:
> 
> One little detail that jumped at me just now: the automarkup extension now
> understands Documentation/whatever and makes a cross-reference, so there's
> no need for an explicit :ref: for those.

Ha, cool, thx for the tip, will adjust accordingly!

Ciao, Thorsten