Hi Marcel,

On 04/05/2018 02:23 AM, Marcel Holtmann wrote:

so I took this patch back out of bluetooth-next before sending the pull 
request. I think the discussion on how to fix SHASH_DESC_ON_STACK macro needs 
to complete first. Once that has concluded we can revisit if this patch is 
still needed or if another solution has been found. Same as with WiFi, these 
are not just one-shot calls where a memory allocation doesn’t matter. We need 
this for random address resolution and thus there can be many of the aes_cmac 
calls when seeing neighboring devices.

Yeah. I agree.

Based on Herbert's response to the discussion about SHASH_DESC_ON_STACK https://lkml.org/lkml/2018/3/27/300

it seems it is feasible to fix that macro very easily. I will follow up on this.

By the way, what is you opinion on replacing crypto_shash_descsize(ctx) with PAGE_SIZE / 8 in SHASH_DESC_ON_STACK?

Does it work for you?


Reply via email to