linux-kernel - Re: 2.6.22-rc6-mm1 Intel DMAR crash on AMD x86

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: <p73645543xk.fsf@bingen.suse.de>
Date:	30 Jun 2007 21:50:47 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Muli Ben-Yehuda <muli@...ibm.com>
Cc:	"Keshavamurthy, Anil S" <anil.s.keshavamurthy@...el.com>,
	Robert Hancock <hancockr@...w.ca>, Zan Lynx <zlynx@....org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, "Raj, Ashok" <ashok.raj@...el.com>
Subject: Re: 2.6.22-rc6-mm1 Intel DMAR crash on AMD x86_64

Muli Ben-Yehuda <muli@...ibm.com> writes:
> 
> The convention is to print a KERN_DEBUG message if hardware is not
> found when probing it, otherwise the boot messages become cluttered
> with lots of "$FOO not found".

No the convention is to print no message at all when nothing is found
Some drivers fail this, but they're bad examples.

-Andi
-
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/