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: <38BC2B4F-4050-4060-9FF0-54212DE3E1CF@linaro.org> Date: Mon, 17 Oct 2016 10:49:01 +0100 From: Ard Biesheuvel <ard.biesheuvel@...aro.org> To: Johannes Berg <johannes@...solutions.net> 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 > On 17 Oct 2016, at 10:35, Johannes Berg <johannes@...solutions.net> wrote: > >> On Mon, 2016-10-17 at 10:30 +0100, Ard Biesheuvel wrote: >> >> Yes. But as I replied, setting the req size is not supported atm, >> although it is reasonable to demand a way to allocate additional data >> in the request specifically for this issue. So let's proceed with the >> aead_request_alloc/free patch, but I would like to propose something >> on the API side to address this particular issue > > Well, if your other patch to make it OK to be on-stack would be applied > instead, this wouldn't make much sense either :) > > In this particular patch, we could reduce the size of the struct, but I > don't actually think it'll make a difference to go from 48 to 36 bytes, > given alignment etc., so I think I'll just leave it as is. > > johannes
Powered by blists - more mailing lists