Received: by 2002:a05:6a10:9afc:0:0:0:0 with SMTP id t28csp1585874pxm; Thu, 3 Mar 2022 22:35:51 -0800 (PST) X-Google-Smtp-Source: ABdhPJyc51LuxGrmaplsiVyOI50zBlR4q4oAvopSvwXZcYDMxmVKtnhhL4KQiXqvIMY711XEwGGu X-Received: by 2002:a17:902:da91:b0:151:8e79:8307 with SMTP id j17-20020a170902da9100b001518e798307mr14705712plx.8.1646375751676; Thu, 03 Mar 2022 22:35:51 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1646375751; cv=none; d=google.com; s=arc-20160816; b=sB1KlV50DIFLUZ47BsDE0y2i9bdROq7E9H2Ut8AVtR7IMCU0xo6TC739TZACc0qWP8 vBxGD1QbrTye1gbdfr/Z2ueqNPLDKVRJ+pXmgz93+yrYku6HkvDAZaTcRc6h4DSRN98b qET7dpirGhQCHzB4m+fiCBTH+0qZ9tvrfz5Lim+YnTdqSaStkvJ4F4kvsj/wJKe3ql0r aurY5wf6akIU95KipLKw2xAy8cYylTsiGkfxVanlaSCmFZ5C7df0+SLibWV/LjyfeRdt 87PGUXExHDDSx5g2q9GrAz9ArhCnmoW9AnmS0BF7czBbVYK5yvio10llXDVdua1fMdXN MO8Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=zsIbz0/b386hU/ZdkOSBubB6mU+6IwbbmnEE1Ycu+MY=; b=JmT9WooT2gfmTDkjKUBse7vN5QZ3DM2/A/t77ILoAAhtX5yCOr/Mn1nlePAg9vXuta eRFHrah3TEaaiTYvijr8vPVtC2b6n9nO6JtpANTT6k1h3+0hbNVhuiIIcGLgbpP8plDn +GKia5wxn9grv6ogoLDJtNGSoimZu/nqKRl6GlZ8p+zgXFUxZi4ukNPY/uv9V6/Vxy34 AkWunAwVdx0TywCpWA4jX/fKdmof6tv9FEiWiKUkjcu3F1toJ2KwLzdnZUBXZr2JWyob 4ALR6IPZPQBuZ4EL5Icn7kFDAioj7QdcsthWkxdZSvwp84KBzahZgPALQF7ZptZDyWyY qXRw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@baylibre-com.20210112.gappssmtp.com header.s=20210112 header.b="P2/lLp3f"; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id s3-20020a632c03000000b0037c46b06bf1si3820107pgs.619.2022.03.03.22.35.36; Thu, 03 Mar 2022 22:35:51 -0800 (PST) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@baylibre-com.20210112.gappssmtp.com header.s=20210112 header.b="P2/lLp3f"; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229981AbiCCTzu (ORCPT + 99 others); Thu, 3 Mar 2022 14:55:50 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46262 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235269AbiCCTzu (ORCPT ); Thu, 3 Mar 2022 14:55:50 -0500 Received: from mail-wr1-x435.google.com (mail-wr1-x435.google.com [IPv6:2a00:1450:4864:20::435]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C01ED18A794 for ; Thu, 3 Mar 2022 11:55:03 -0800 (PST) Received: by mail-wr1-x435.google.com with SMTP id j17so9545002wrc.0 for ; Thu, 03 Mar 2022 11:55:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20210112.gappssmtp.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to; bh=zsIbz0/b386hU/ZdkOSBubB6mU+6IwbbmnEE1Ycu+MY=; b=P2/lLp3fpnzXDyB/a8TOfUWFAEABVhPQyw4vrBIqcCPNSqVsh75hfUEo7ksNNW/Lcb ORQN/swrL9IYwChFBbsy08B20shjCFURo9fA0UgjDt75cIZKeskIDctWDweIMszbiF6m 3+nmbWDgvuxmybGFmrYHRHpPTjZCB/qljmJZ3vd6zWuX2A0yZ1UHZY77KScrPe2Ub+16 4cEBAP5AxkTO00SGIVZ8/zdzMBBN5llAfSpc1JftBSSCtowCDLpqBx1t2zciHAwnwV+W 7sLq/+PwEBc8tt8f0vczCDQUcL29TKHITgigXYDaIVbTLoXTERVs1vX0tt/vf35T8kAu f+tw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to; bh=zsIbz0/b386hU/ZdkOSBubB6mU+6IwbbmnEE1Ycu+MY=; b=xAs7GJK5WDYuGIRBOaoeqNZwLhqe3OiwzoB93RUE0/XOn11Xfx96YAC3DflA+kLae/ BqEN+UWotjUW1NpsT+LVtoj8cyH/X2SV/iXkuuJOHVBcHzsOebFCN27//g5eRXPBoBnW 3tHtsu0EAZFZBtRT92ua/OTJaBHnV67k6fo1GFRBq5AyGqrvLRixnioHpDynTHzgmCIZ MCFawqUslFpL4L8xsMgpbKC8sdpoezVxXiS7JR+VFgrZj+Fm2BvjzkbjWL/69JvVs/4C KE4jNs5Cadq7YmpujhOXAuTG9uLXIOqIDqsCiZw+VTbKzQFuSeXbRVsDYIPVxu5gWe0L sZrg== X-Gm-Message-State: AOAM53172/BHhzVEoDErKe4xLHonzAROMZ+oSEOFLqVaIkZtHy+J3TQC lrOrosOfafZI8yk7HzilZZwxnw== X-Received: by 2002:a5d:5407:0:b0:1f0:1246:5a8c with SMTP id g7-20020a5d5407000000b001f012465a8cmr10294116wrv.193.1646337302326; Thu, 03 Mar 2022 11:55:02 -0800 (PST) Received: from Red ([2a01:cb1d:3d5:a100:264b:feff:fe03:2806]) by smtp.googlemail.com with ESMTPSA id x2-20020a7bc762000000b00380fd1ba4ebsm16466518wmk.9.2022.03.03.11.55.01 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 03 Mar 2022 11:55:01 -0800 (PST) Date: Thu, 3 Mar 2022 20:54:58 +0100 From: LABBE Corentin To: John Keeping Cc: heiko@sntech.de, herbert@gondor.apana.org.au, robh+dt@kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org Subject: Re: [PATCH v2 06/18] crypto: rockchip: add fallback for cipher Message-ID: References: <20220302211113.4003816-1-clabbe@baylibre.com> <20220302211113.4003816-7-clabbe@baylibre.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org Le Thu, Mar 03, 2022 at 02:21:37PM +0000, John Keeping a ?crit : > On Wed, Mar 02, 2022 at 09:11:01PM +0000, Corentin Labbe wrote: > > The hardware does not handle 0 size length request, let's add a > > fallback. > > Furthermore fallback will be used for all unaligned case the hardware > > cannot handle. > > > > Fixes: ce0183cb6464b ("crypto: rockchip - switch to skcipher API") > > Signed-off-by: Corentin Labbe > > --- > > drivers/crypto/rockchip/rk3288_crypto.h | 2 + > > .../crypto/rockchip/rk3288_crypto_skcipher.c | 97 ++++++++++++++++--- > > 2 files changed, 86 insertions(+), 13 deletions(-) > > > > diff --git a/drivers/crypto/rockchip/rk3288_crypto.h b/drivers/crypto/rockchip/rk3288_crypto.h > > index c919d9a43a08..8b1e15d8ddc6 100644 > > --- a/drivers/crypto/rockchip/rk3288_crypto.h > > +++ b/drivers/crypto/rockchip/rk3288_crypto.h > > @@ -246,10 +246,12 @@ struct rk_cipher_ctx { > > struct rk_crypto_info *dev; > > unsigned int keylen; > > u8 iv[AES_BLOCK_SIZE]; > > + struct crypto_skcipher *fallback_tfm; > > }; > > > > struct rk_cipher_rctx { > > u32 mode; > > + struct skcipher_request fallback_req; // keep at the end > > }; > > > > enum alg_type { > > diff --git a/drivers/crypto/rockchip/rk3288_crypto_skcipher.c b/drivers/crypto/rockchip/rk3288_crypto_skcipher.c > > index bbd0bf52bf07..bf9d398cc54c 100644 > > --- a/drivers/crypto/rockchip/rk3288_crypto_skcipher.c > > +++ b/drivers/crypto/rockchip/rk3288_crypto_skcipher.c > > @@ -13,6 +13,63 @@ > > > > #define RK_CRYPTO_DEC BIT(0) > > > > +static int rk_cipher_need_fallback(struct skcipher_request *req) > > +{ > > + struct scatterlist *sgs, *sgd; > > + > > + if (!req->cryptlen) > > + return true; > > + > > + sgs = req->src; > > + while (sgs) { > > + if (!IS_ALIGNED(sgs->offset, sizeof(u32))) { > > + return true; > > + } > > + if (sgs->length % 16) { > > Can this be relaxed to check for alignment to 4 rather than 16? That's > the requirement for programming the registers. No we cannot, the hardware could operate only one SG at a time, and the cipher operation need to be complete, so the length should be a multiple of AES_BLOCK_SIZE. The original driver already have this size check. But for DES/3DES this check is bad and should be 8, so a fix is needed anyway. > > But I think this check is wrong in general as it doesn't account for > cryptlen; with fscrypt I'm seeing sgs->length == 255 but cryptlen == 16 > so the hardware can be used but at the moment the fallback path is > triggered. Yes, I need to check min(sg->length, cryptlen_remaining) instead. I will fix that. Thanks.