Return-path: Received: from s3.sipsolutions.net ([5.9.151.49]:49102 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933019AbcJQHsG (ORCPT ); Mon, 17 Oct 2016 03:48:06 -0400 Message-ID: <1476690478.19992.4.camel@sipsolutions.net> (sfid-20161017_094832_764117_59E1D493) Subject: Re: [PATCH] crypto: ccm - avoid scatterlist for MAC encryption From: Johannes Berg To: Ard Biesheuvel Cc: Andy Lutomirski , Sergey Senozhatsky , "" , Herbert Xu , "David S. Miller" , "" , "linux-kernel@vger.kernel.org" , Jouni Malinen Date: Mon, 17 Oct 2016 09:47:58 +0200 In-Reply-To: (sfid-20161017_093746_906697_1D2C1C61) References: <1476551776-8099-1-git-send-email-ard.biesheuvel@linaro.org> <1476689310.19992.1.camel@sipsolutions.net> (sfid-20161017_093746_906697_1D2C1C61) Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Mon, 2016-10-17 at 08:37 +0100, Ard Biesheuvel wrote: >  > Could we get a statement first whether it is supported to allocate > aead_req (and other crypto req structures) on the stack? Well, we haven't heard from Herbert :) > If not, then > we have our work cut out for us. But if it is, I'd rather we didn't > apply the kzalloc/kfree patch, since it is just a workaround for the > broken generic CCM driver, for which a fix is already available. Yeah but I can't apply it. I just fixed up your kzalloc patch to also handle GCM and GMAC, and to have error checking. Will send it in a minute. > Also, regarding your __percpu patch: those are located in the vmalloc > area as well, at least on arm64, and likely other architectures too. Crap. Any other bright ideas? johannes