Received: by 2002:a05:6358:a55:b0:ec:fcf4:3ecf with SMTP id 21csp2331509rwb; Fri, 20 Jan 2023 01:14:04 -0800 (PST) X-Google-Smtp-Source: AMrXdXv/YWiYxSVL34ev2cPzSiZui3Ny3r8Gn9VG+iDFAgxKSnZvDv9LYJFoToKJ7JtNEILCaXLn X-Received: by 2002:aa7:c1d7:0:b0:479:971e:58f6 with SMTP id d23-20020aa7c1d7000000b00479971e58f6mr13735821edp.19.1674206043591; Fri, 20 Jan 2023 01:14:03 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1674206043; cv=none; d=google.com; s=arc-20160816; b=uZVsJwTQmHqZatedsImtGHvGOqMDA/JPzAWzbP0ZaLv5x0MqVkdJ8GgSbGrAGaVgII HuKioD5MksTm9zPf6RG7KsqgRpJY+O3L3GH319PwahRsBYcZHrlS8vVHL/NNeRflssks 6Gbh9Nekjg0JUyYuYLxctDsX34X2guEXbQZbpgz98axzF/2Qyl+u6H1QI1pKR426tkw/ FLs/2+zhJgUO9Ly0OD5piLuUF6OjjTNuioB8dGFW9GVheMyNiiocXH2Q/GChR4zTsJy3 fvaNaCYiVrh5AAdFTpGre04y0A1zKtpSkEdr9ogWjK1w3Mb2XwDvX43ZSvWlZ1uh20Ai GaZA== 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-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=0nP8N4AVN0Zei5n+gOrjT4Adec+EV5B+d7L9Ni36Zmg=; b=0S56UT2+XRMqMHLHwRW4SuYXEx64KcpOrR4T1zSpG+oFqSjCwo3yp0HNLpYVzfnkG3 F/0e6nXyE1sKHgIzTovrjbpfq6I/rbUZZFrfBNFNgFppEVDRHxfFsWDD6A1pd9nK+f8W 10U7jy4hkxiV+sqP6nk9lytHTYjcdtxUgw+4sUZX9flj7XbErEKPdJscaGsow2hWTMrk 14ZJGKooPjA2bwLsmapWrVFygg1alG9YEJfqpO2OeI67Y+rVriy12t3PWhKx8dyJu6Eu AFKg2LxHugcPkI/HV5mLEqCRRnOs59o8lONjzvRzT2968IS2BBQo7763HYye2cQkVMpj UnAA== ARC-Authentication-Results: i=1; mx.google.com; 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 gs44-20020a1709072d2c00b0084d354539a5si45219676ejc.584.2023.01.20.01.13.40; Fri, 20 Jan 2023 01:14:03 -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; 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 S229918AbjATJNC (ORCPT + 99 others); Fri, 20 Jan 2023 04:13:02 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52002 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229916AbjATJNB (ORCPT ); Fri, 20 Jan 2023 04:13:01 -0500 Received: from formenos.hmeau.com (helcar.hmeau.com [216.24.177.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3B8548C939; Fri, 20 Jan 2023 01:12:31 -0800 (PST) Received: from loth.rohan.me.apana.org.au ([192.168.167.2]) by formenos.hmeau.com with smtp (Exim 4.94.2 #2 (Debian)) id 1pInR9-0029bo-CL; Fri, 20 Jan 2023 17:11:52 +0800 Received: by loth.rohan.me.apana.org.au (sSMTP sendmail emulation); Fri, 20 Jan 2023 17:11:51 +0800 Date: Fri, 20 Jan 2023 17:11:51 +0800 From: Herbert Xu To: Vincent Whitchurch Cc: davem@davemloft.net, jesper.nilsson@axis.com, lars.persson@axis.com, kernel@axis.com, linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 02/12] crypto: axis - do not DMA to IV Message-ID: References: <20230110135042.2940847-1-vincent.whitchurch@axis.com> <20230110135042.2940847-3-vincent.whitchurch@axis.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230110135042.2940847-3-vincent.whitchurch@axis.com> X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_PASS autolearn=ham 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 On Tue, Jan 10, 2023 at 02:50:32PM +0100, Vincent Whitchurch wrote: > The crypto API does not promise that the IV buffer is suitable for DMA. > Use an intermediate buffer instead. > > Signed-off-by: Vincent Whitchurch > --- > drivers/crypto/axis/artpec6_crypto.c | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) > > diff --git a/drivers/crypto/axis/artpec6_crypto.c b/drivers/crypto/axis/artpec6_crypto.c > index 87af44ac3e64..d3b6ee065a81 100644 > --- a/drivers/crypto/axis/artpec6_crypto.c > +++ b/drivers/crypto/axis/artpec6_crypto.c > @@ -321,6 +321,7 @@ struct artpec6_crypto_request_context { > u32 cipher_md; > bool decrypt; > struct artpec6_crypto_req_common common; > + unsigned char iv_bounce[AES_BLOCK_SIZE] CRYPTO_MINALIGN_ATTR; Please use the newly introduced CRYPTO_DMA_ALIGN macro. CRYPTO_MINALIGN only reflects minimum kmalloc alignment, which may be less than that required for DMA. You're currently safe on arm32, but we should not rely on this in new code. Thanks, -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt