| 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
| ||
|
Message-ID: <AANLkTiky-saTpv6Vq2ipIWC39b5eox92qQGE0QcACEBR@mail.gmail.com> Date: Wed, 19 May 2010 15:54:43 +0300 From: Pekka Enberg <penberg@...helsinki.fi> To: Herbert Xu <herbert@...dor.apana.org.au> Cc: David Woodhouse <dwmw2@...radead.org>, David Miller <davem@...emloft.net>, mpm@...enic.com, ken@...elabs.ch, geert@...ux-m68k.org, michael-dev@...i-braun.de, linux-kernel@...r.kernel.org, linux-crypto@...r.kernel.org, anemo@....ocn.ne.jp Subject: Re: [BUG] SLOB breaks Crypto On Wed, May 19, 2010 at 2:46 PM, Herbert Xu <herbert@...dor.apana.org.au> wrote: > On Wed, May 19, 2010 at 12:16:45PM +0100, David Woodhouse wrote: >> >> I don't mind. Feel free to apply them to slab.git, but be aware that >> Herbert wanted to see a patch fixing sparc32 ARCH_SLAB_MINALIGN before >> the crypto one is applied. >> >> Although arguably SLOB was broken on sparc32 even before the crypto >> patch -- so perhaps that fix shouldn't _have_ to go in first? > > Well prior to this crypto on sparc32 did work with SLAB/SLUB. If > you change it without including the sparc pach, then sparc32 would > be broken regardless of which allocator you used. OK, I'll pick up David's patches and just wait for sparc changes to hit Linus' tree first. Herbert, do I have your ACK for the crypto patches? -- 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