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: Thu, 5 Aug 2010 19:01:21 -0700 From: Linus Torvalds <torvalds@...ux-foundation.org> To: Herbert Xu <herbert@...dor.hengli.com.au> Cc: David Howells <dhowells@...hat.com>, gregkh@...e.de, linux-kernel@...r.kernel.org, linux-crypto@...r.kernel.org Subject: Re: Initcall ordering problem (TTY vs modprobe vs MD5) and cryptomgr problem On Thu, Aug 5, 2010 at 6:40 PM, Herbert Xu <herbert@...dor.hengli.com.au> wrote: > > -config CRYPTO_MANAGER_TESTS > - bool "Run algolithms' self-tests" > - default y > - depends on CRYPTO_MANAGER2 > +config CRYPTO_MANAGER_DISABLE_TESTS > + bool "Disable run-time self tests" > + depends on CRYPTO_MANAGER2 && EMBEDDED Why do you still want to force-enable those tests? I was going to complain about the "default y" anyway, now I'm _really_ complaining, because you've now made it impossible to disable those tests. Why? People always think that their magical code is so important. I tell you up-front that is absolutely is not. Just remove the crap entirely, please. Linus -- 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