linux-kernel - Disabling lock debugging due to kernel taint

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>] [day] [month] [year] [list]

Message-ID: <4A9AB806.2020906@imap.cc>
Date:	Sun, 30 Aug 2009 19:33:58 +0200
From:	Tilman Schmidt <tilman@...p.cc>
To:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Disabling lock debugging due to kernel taint

In 2.6.31-rc the kernel has sprouted the message in the subject.
Now I completely understand the motivation behind this. Nobody
wants to spend time on problem reports that ultimately turn out
to be caused by closed-source code. But for a maintainer of a
(GPLed) driver like me who happens to need a proprietary
graphics driver it does cause some inconvenience.

Is there a simple way to get lock debugging even with a
proprietary graphics driver?

Thanks,
Tilman

-- 
Tilman Schmidt                    E-Mail: tilman@...p.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)

Download attachment "signature.asc" of type "application/pgp-signature" (255 bytes)