[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CALCETrWRyai42BbQ213TzmZ9KwQhAD2eEoeCeR+6NPSC4O4BZg@mail.gmail.com>
Date: Thu, 23 Jun 2016 15:11:00 -0700
From: Andy Lutomirski <luto@...capital.net>
To: Herbert Xu <herbert@...dor.apana.org.au>
Cc: Andy Lutomirski <luto@...nel.org>, linux-bluetooth@...r.kernel.org,
Johan Hedberg <johan.hedberg@...il.com>,
Gustavo Padovan <gustavo@...ovan.org>,
Marcel Holtmann <marcel@...tmann.org>,
linux-crypto@...r.kernel.org,
"David S. Miller" <davem@...emloft.net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Network Development <netdev@...r.kernel.org>
Subject: Re: Doing crypto in small stack buffers (bluetooth vs vmalloc-stack
crash, etc)
On Wed, Jun 22, 2016 at 11:41 PM, Herbert Xu
<herbert@...dor.apana.org.au> wrote:
> On Thu, Jun 23, 2016 at 11:48:25AM +0800, Herbert Xu wrote:
>>
>> No we never had such an API in the kernel. However, I see that
>> rxkad does some pretty silly things and we should be able to avoid
>> using the stack in pretty much all cases. Let me try to come up with
>> something.
>
> Here it is:
>
> ---8<---
> Subject: rxrpc: Avoid using stack memory in SG lists in rxkad
Looks reasonable to me. Unless anyone tells me otherwise, my plan is
to queue it in my virtually-mapped stack series and to ask Ingo to
apply it via -tip.
If it went in via the networking tree, that would work as well, but it
would introduce a bisectability problem.
Thanks!
--Andy
Powered by blists - more mailing lists