mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: Alexey Romanov <avromanov@salutedevices.com>
To: <narmstrong@baylibre.com>, <neil.armstrong@linaro.org>,
	<clabbe@baylibre.com>, <herbert@gondor.apana.org.au>,
	<davem@davemloft.net>, <robh+dt@kernel.org>,
	<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
	<khilman@baylibre.com>, <jbrunet@baylibre.com>,
	<artin.blumenstingl@googlemail.com>
Cc: <linux-crypto@vger.kernel.org>,
	<linux-amlogic@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<kernel@salutedevices.com>,
	Jan Dakinevich <yvdakinevich@salutedevices.com>,
	Alexey Romanov <avromanov@salutedevices.com>
Subject: [PATCH v1 10/24] drivers: crypto: meson: avoid kzalloc in engine thread
Date: Wed, 10 Jan 2024 23:11:26 +0300	[thread overview]
Message-ID: <20240110201216.18016-11-avromanov@salutedevices.com> (raw)
In-Reply-To: <20240110201216.18016-1-avromanov@salutedevices.com>

From: Jan Dakinevich <yvdakinevich@salutedevices.com>

It makes no sense to allocate memory via kzalloc, we
can use static buffer, speedup data processing and
don't think about kfree() calls.

Signed-off-by: Jan Dakinevich <yvdakinevich@salutedevices.com>
Signed-off-by: Alexey Romanov <avromanov@salutedevices.com>
---
 drivers/crypto/amlogic/amlogic-gxl-cipher.c | 24 ++++++++-------------
 drivers/crypto/amlogic/amlogic-gxl.h        |  6 +++---
 2 files changed, 12 insertions(+), 18 deletions(-)

diff --git a/drivers/crypto/amlogic/amlogic-gxl-cipher.c b/drivers/crypto/amlogic/amlogic-gxl-cipher.c
index 59b1c754d326..6ff0e088939f 100644
--- a/drivers/crypto/amlogic/amlogic-gxl-cipher.c
+++ b/drivers/crypto/amlogic/amlogic-gxl-cipher.c
@@ -155,8 +155,7 @@ static void meson_setup_keyiv_descs(struct cipher_ctx *ctx)
 		return;
 
 	if (blockmode == DESC_OPMODE_CBC) {
-		memcpy(op->key + AES_MAX_KEY_SIZE, ctx->areq->iv, ivsize);
-		ctx->keyiv.len = AES_MAX_KEY_SIZE + ivsize;
+		memcpy(op->keyiv + AES_MAX_KEY_SIZE, ctx->areq->iv, ivsize);
 		dma_sync_single_for_device(mc->dev, ctx->keyiv.addr,
 					   ctx->keyiv.len, DMA_TO_DEVICE);
 	}
@@ -319,16 +318,16 @@ static int meson_cipher(struct skcipher_request *areq)
 	mc->chanlist[rctx->flow].stat_req++;
 #endif
 
-	op->key = kzalloc(48, GFP_KERNEL | GFP_DMA);
-	if (!op.key)
-		return -ENOMEM;
-
-	memcpy(op->key, op->key, op->keylen);
 	ctx.keyiv.len = op->keylen;
 	if (ctx.keyiv.len == AES_KEYSIZE_192)
 		ctx.keyiv.len = AES_MAX_KEY_SIZE;
 
-	ctx.keyiv.addr = dma_map_single(mc->dev, op->key, ctx.keyiv.len,
+	if (algt->blockmode == DESC_OPMODE_CBC) {
+		memcpy(op->keyiv + AES_MAX_KEY_SIZE, areq->iv, ivsize);
+		ctx.keyiv.len = AES_MAX_KEY_SIZE + ivsize;
+	}
+
+	ctx.keyiv.addr = dma_map_single(mc->dev, op->keyiv, ctx.keyiv.len,
 				  DMA_TO_DEVICE);
 	err = dma_mapping_error(mc->dev, ctx.keyiv.addr);
 	if (err) {
@@ -366,8 +365,6 @@ static int meson_cipher(struct skcipher_request *areq)
 	meson_unmap_scatterlist(areq, mc);
 
 theend:
-	kfree_sensitive(op->key);
-
 	return err;
 }
 
@@ -455,7 +452,6 @@ static void meson_cipher_exit(struct crypto_tfm *tfm)
 {
 	struct meson_cipher_tfm_ctx *op = crypto_tfm_ctx(tfm);
 
-	kfree_sensitive(op->key);
 	crypto_free_skcipher(op->fallback_tfm);
 }
 
@@ -479,11 +475,9 @@ static int meson_aes_setkey(struct crypto_skcipher *tfm, const u8 *key,
 		dev_dbg(mc->dev, "ERROR: Invalid keylen %u\n", keylen);
 		return -EINVAL;
 	}
-	kfree_sensitive(op->key);
+
+	memcpy(op->keyiv, key, keylen);
 	op->keylen = keylen;
-	op->key = kmemdup(key, keylen, GFP_KERNEL | GFP_DMA);
-	if (!op->key)
-		return -ENOMEM;
 
 	return crypto_skcipher_setkey(op->fallback_tfm, key, keylen);
 }
diff --git a/drivers/crypto/amlogic/amlogic-gxl.h b/drivers/crypto/amlogic/amlogic-gxl.h
index 36628a7a4cf3..2eeafdca1669 100644
--- a/drivers/crypto/amlogic/amlogic-gxl.h
+++ b/drivers/crypto/amlogic/amlogic-gxl.h
@@ -128,7 +128,7 @@ struct meson_cipher_req_ctx {
 /*
  * struct meson_cipher_tfm_ctx - context for a skcipher TFM
  * @enginectx:		crypto_engine used by this TFM
- * @key:		pointer to key data
+ * @keyiv:		key data
  * @keylen:		len of the key
  * @keymode:		The keymode(type and size of key) associated with this TFM
  * @mc:			pointer to the private data of driver handling this TFM
@@ -136,8 +136,8 @@ struct meson_cipher_req_ctx {
  */
 struct meson_cipher_tfm_ctx {
 	struct crypto_engine_ctx enginectx;
-	u32 *key;
-	u32 keylen;
+	u8 keyiv[AES_MAX_KEY_SIZE + AES_BLOCK_SIZE] ____cacheline_aligned;
+	u32 keylen ____cacheline_aligned;
 	u32 keymode;
 	struct meson_dev *mc;
 	struct crypto_skcipher *fallback_tfm;
-- 
2.30.1


_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

  parent reply	other threads:[~2024-01-10 20:13 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-10 20:11 [PATCH v1 00/24] Support more Amlogic SoC families in crypto driver Alexey Romanov
2024-01-10 20:11 ` [PATCH v1 01/24] drivers: crypto: meson: don't hardcode IRQ count Alexey Romanov
2024-01-11  8:21   ` neil.armstrong
2024-01-10 20:11 ` [PATCH v1 02/24] drivers: crypto: meson: make CLK controller optional Alexey Romanov
2024-01-11  8:20   ` neil.armstrong
2024-01-10 20:11 ` [PATCH v1 03/24] drviers: crypto: meson: add platform data Alexey Romanov
2024-01-10 20:11 ` [PATCH v1 04/24] drivers: crypto: meson: add MMIO helpers Alexey Romanov
2024-01-10 20:11 ` [PATCH v1 05/24] drivers: crypto: meson: move get_engine_number() Alexey Romanov
2024-01-10 20:11 ` [PATCH v1 06/24] drivers: crypto: meson: drop status field from meson_flow Alexey Romanov
2024-01-10 20:11 ` [PATCH v1 07/24] drivers: crypto: meson: move algs definition and cipher API to cipher.c Alexey Romanov
2024-01-10 20:11 ` [PATCH v1 08/24] drivers: crypto: meson: cleanup defines Alexey Romanov
2024-01-10 20:11 ` [PATCH v1 09/24] drivers: crypto: meson: process more than MAXDESCS descriptors Alexey Romanov
2024-01-10 20:11 ` Alexey Romanov [this message]
2024-01-10 20:11 ` [PATCH v1 11/24] drivers: crypto: meson: introduce hasher Alexey Romanov
2024-01-10 20:11 ` [PATCH v1 12/24] drivers: crypto: meson: add support for AES-CTR Alexey Romanov
2024-01-10 20:11 ` [PATCH v1 13/24] drivers: crypto: meson: use fallback for 192-bit keys Alexey Romanov
2024-01-10 20:11 ` [PATCH v1 14/24] drivers: crypto: meson: add support for G12-series Alexey Romanov
2024-01-10 20:11 ` [PATCH v1 15/24] drivers: crypto: meson: add support for AXG-series Alexey Romanov
2024-01-10 20:11 ` [PATCH v1 16/24] dt-bindings: crypto: meson: add new compatibles Alexey Romanov
2024-01-10 21:25   ` Rob Herring
2024-01-11  1:44   ` Rob Herring
2024-01-11  8:15   ` neil.armstrong
2024-01-10 20:11 ` [PATCH v1 17/24] arch: arm64: dts: meson: a1: add crypto node Alexey Romanov
2024-01-11  8:16   ` neil.armstrong
2024-01-10 20:11 ` [PATCH v1 18/24] arch: arm64: dts: meson: s4: " Alexey Romanov
2024-01-10 20:11 ` [PATCH v1 19/24] arch: arm64: dts: meson: g12: " Alexey Romanov
2024-01-10 20:11 ` [PATCH v1 20/24] arch: arm64: dts: meson: axg: " Alexey Romanov
2024-01-10 20:11 ` [PATCH v1 21/24] arch: arm64: dts: meson: s4-s805x2-aq222: enable " Alexey Romanov
2024-01-10 20:11 ` [PATCH v1 22/24] arch: arm64: dts: meson: a1-ad401: " Alexey Romanov
2024-01-10 20:11 ` [PATCH v1 23/24] arch: arm64: dts: meson: axg-s400: " Alexey Romanov
2024-01-10 20:11 ` [PATCH v1 24/24] arch: arm64: dts: meson: g12a-u200: " Alexey Romanov
2024-01-10 21:08 ` [PATCH v1 00/24] Support more Amlogic SoC families in crypto driver Corentin Labbe
2024-01-11  9:18   ` Alexey Romanov
2024-01-11  9:29     ` Krzysztof Kozlowski
2024-01-11  9:31       ` Krzysztof Kozlowski
2024-01-11  8:19 ` neil.armstrong
2024-01-11  9:33   ` Alexey Romanov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240110201216.18016-11-avromanov@salutedevices.com \
    --to=avromanov@salutedevices.com \
    --cc=artin.blumenstingl@googlemail.com \
    --cc=clabbe@baylibre.com \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=jbrunet@baylibre.com \
    --cc=kernel@salutedevices.com \
    --cc=khilman@baylibre.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=narmstrong@baylibre.com \
    --cc=neil.armstrong@linaro.org \
    --cc=robh+dt@kernel.org \
    --cc=yvdakinevich@salutedevices.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®