Messages in this thread | | | From | Andy Lutomirski <> | Date | Thu, 23 Jun 2016 15:11:00 -0700 | 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@gondor.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
| |