On Mon, Sep 30, 2019 at 02:14:34PM +0200, Arnd Bergmann wrote:
> safexcel_aead_setkey() contains three large stack variables, totalling
> slightly more than the 1024 byte warning limit:
>
> drivers/crypto/inside-secure/safexcel_cipher.c:303:12: error: stack frame
> size of 1032 bytes in function
On Mon, Sep 30, 2019 at 11:09 PM Pascal Van Leeuwen
wrote:
> > Subject: Re: [PATCH 2/3] crypto: inside-secure - Reduce stack usage
> >
> > On Mon, Sep 30, 2019 at 9:04 PM Pascal Van Leeuwen
> > wrote:
> >
> > > > Alternatively, it should be possible
cry...@vger.kernel.org; linux-ker...@vger.kernel.org
> Subject: Re: [PATCH 2/3] crypto: inside-secure - Reduce stack usage
>
> On Mon, Sep 30, 2019 at 9:04 PM Pascal Van Leeuwen
> wrote:
>
> > > Alternatively, it should be possible to shrink these allocations
> > > as the ex
On Mon, Sep 30, 2019 at 9:04 PM Pascal Van Leeuwen
wrote:
> > Alternatively, it should be possible to shrink these allocations
> > as the extra buffers appear to be largely unnecessary, but doing
> > this would be a much more invasive change.
> >
> Actually, for HMAC-SHA512 you DO need all that b
-crypto@vger.kernel.org;
> linux-ker...@vger.kernel.org
> Subject: [PATCH 2/3] crypto: inside-secure - Reduce stack usage
>
> safexcel_aead_setkey() contains three large stack variables, totalling
> slightly more than the 1024 byte warning limit:
>
> drivers/crypto/insi
safexcel_aead_setkey() contains three large stack variables, totalling
slightly more than the 1024 byte warning limit:
drivers/crypto/inside-secure/safexcel_cipher.c:303:12: error: stack frame size
of 1032 bytes in function 'safexcel_aead_setkey' [-Werror,-Wframe-larger-than=]
The function alrea
