Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Cc: Neal Liu <neal_liu@aspeedtech.com>, linux-aspeed@lists.ozlabs.org
Subject: [PATCH 00/11] crypto: aspeed/hash - Convert to partial block API
Date: Tue, 13 May 2025 14:03:45 +0800	[thread overview]
Message-ID: <cover.1747116129.git.herbert@gondor.apana.org.au> (raw)

This series converts aspeed to the partial block API while removing
hash length limits and making it more robust if dma mapping fails.

Herbert Xu (11):
  crypto: aspeed/hash - Remove purely software hmac implementation
  crypto: aspeed/hash - Reorganise struct aspeed_sham_reqctx
  crypto: aspeed/hash - Use init_tfm instead of cra_init
  crypto: aspeed/hash - Provide rctx->buffer as argument to fill padding
  crypto: aspeed/hash - Move sham_final call into sham_update
  crypto: aspeed/hash - Move final padding into dma_prepare
  crypto: aspeed/hash - Remove sha_iv
  crypto: aspeed/hash - Use API partial block handling
  crypto: aspeed/hash - Add fallback
  crypto: aspeed/hash - Iterate on large hashes in dma_prepare
  crypto: aspeed/hash - Fix potential overflow in dma_prepare_sg

 drivers/crypto/aspeed/aspeed-hace-hash.c | 802 ++++++-----------------
 drivers/crypto/aspeed/aspeed-hace.h      |  28 +-
 2 files changed, 207 insertions(+), 623 deletions(-)

-- 
2.39.5


             reply	other threads:[~2025-05-13  6:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-13  6:03 Herbert Xu [this message]
2025-05-13  6:03 ` [PATCH 01/11] crypto: aspeed/hash - Remove purely software hmac implementation Herbert Xu
2025-05-13  6:03 ` [PATCH 02/11] crypto: aspeed/hash - Reorganise struct aspeed_sham_reqctx Herbert Xu
2025-05-13  6:03 ` [PATCH 03/11] crypto: aspeed/hash - Use init_tfm instead of cra_init Herbert Xu
2025-05-13  6:03 ` [PATCH 04/11] crypto: aspeed/hash - Provide rctx->buffer as argument to fill padding Herbert Xu
2025-05-13  6:03 ` [PATCH 05/11] crypto: aspeed/hash - Move sham_final call into sham_update Herbert Xu
2025-05-13  6:03 ` [PATCH 06/11] crypto: aspeed/hash - Move final padding into dma_prepare Herbert Xu
2025-05-13  6:04 ` [PATCH 07/11] crypto: aspeed/hash - Remove sha_iv Herbert Xu
2025-05-13  6:04 ` [PATCH 08/11] crypto: aspeed/hash - Use API partial block handling Herbert Xu
2025-05-13  6:04 ` [PATCH 09/11] crypto: aspeed/hash - Add fallback Herbert Xu
2025-05-13  6:04 ` [PATCH 10/11] crypto: aspeed/hash - Iterate on large hashes in dma_prepare Herbert Xu
2025-05-13  6:04 ` [PATCH 11/11] crypto: aspeed/hash - Fix potential overflow in dma_prepare_sg Herbert Xu

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=cover.1747116129.git.herbert@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=neal_liu@aspeedtech.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