linux-kernel - Re: [PATCH 03/10] crypto: Add support for x86 cpuid auto loading for x86 crypto drivers

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

Message-ID: <4EF014FE.4050101@zytor.com>
Date:	Mon, 19 Dec 2011 20:54:22 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Andi Kleen <andi@...stfloor.org>
CC:	Dave Jones <davej@...hat.com>, linux-kernel@...r.kernel.org,
	trenn@...e.de, kay.sievers@....org,
	Andi Kleen <ak@...ux.intel.com>, kay.sievers@...y.org,
	axboe@...nel.dk, herbert@...dor.hengli.com.au, ying.huang@...el.com
Subject: Re: [PATCH 03/10] crypto: Add support for x86 cpuid auto loading
 for x86 crypto drivers

On 12/19/2011 08:08 PM, Andi Kleen wrote:
>> The first printk is insanely annoying, because the end result is that we
>> get a printk of all the crypto engines that are *not* enabled...
>> arguably it would be somewhat nice to get a printk when a crypto engine
>> *is* enabled.
> 
> Yes that was my rationale. I have some Intel system complaining that
> some VIA crypto is not available. That's very annoying and just has
> to go.

What is really bad is that it doesn't tell you anywhere what it *is* using.

	-hpa


-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

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