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, 24 Apr 2008 00:28:43 +0200 From: Sebastian Siewior <linux-crypto@...breakpoint.cc> To: Herbert Xu <herbert@...dor.apana.org.au> Cc: "Huang, Ying" <ying.huang@...el.com>, "Adam J. Richter" <adam@...drasil.com>, akpm@...ux-foundation.org, linux-kernel@...r.kernel.org, linux-crypto@...r.kernel.org, mingo@...e.hu, tglx@...utronix.de Subject: Re: [PATCH -mm crypto] AES: x86_64 asm implementation optimization * Herbert Xu | 2008-04-17 11:34:02 [+0800]: >On Thu, Apr 17, 2008 at 09:52:03AM +0800, Huang, Ying wrote: >> >> As far as I know, the CRYPTO_MINALIGN is defined in >> include/linux/crypto.h as __alignof__(unsigned long long), and the >> __crt_ctx in crypto_tfm is aligned in CRYPTO_MINALIGN. So I think adding >> a pad is sufficient for x86_64 implementation. > >It should be sufficient but it would be better to use an align Doesn't this imply that kmalloc() returns memory that is always pointer aligned what isn't the case AFAIK? >Thanks, Sebastian -- 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