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: <1476710706.315.2.camel@sipsolutions.net> Date: Mon, 17 Oct 2016 15:25:06 +0200 From: Johannes Berg <johannes@...solutions.net> To: Ard Biesheuvel <ard.biesheuvel@...aro.org> Cc: "<linux-wireless@...r.kernel.org>" <linux-wireless@...r.kernel.org>, Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>, "<netdev@...r.kernel.org>" <netdev@...r.kernel.org>, Herbert Xu <herbert@...dor.apana.org.au> Subject: Re: [PATCH v4] mac80211: move extra crypto data off the stack > Indeed. And it keeps the clutter inside the aes_xxx.c files, which > could easily be updated in the future to use some auxdata feature if > it ever materializes. > > I think it would help this code, but also the ESP code you pointed > out, to have some kind of 'ordered synchronous' CRYPTO_xxx flag, > where the crypto API could manage the kmem cache and percpu pointers > to allocations. Yeah, could be useful to have that more generally. > This goes well beyond what we can do as a fix, though, so we need an > intermediate solution in any case. > > Shall I propose the patch? I assume you mean a mac80211 patch - sure, I'll take that instead of the two I have now. johannes
Powered by blists - more mailing lists