| 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
| ||
|
Date: Fri, 16 Dec 2011 10:27:24 +0100 From: "Arend van Spriel" <arend@...adcom.com> To: "linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org> cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: unexpected taint message To whoever may know, Upon loading our driver module I get the following message: kernel: [ 344.805106] Disabling lock debugging due to kernel taint What exactly are the criteria for tainting? Our driver locking strategy is something we want to refactor and having lock debugging during that transition may be a life safer. Gr. AvS -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists