From: Eric Biggers <ebiggers@kernel.org>
To: linux-crypto@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
"Jason A . Donenfeld" <Jason@zx2c4.com>,
qat-linux@intel.com,
Giovanni Cabiddu <giovanni.cabiddu@intel.com>,
Ovidiu Panait <ovidiu.panait.oss@gmail.com>,
Eric Biggers <ebiggers@kernel.org>
Subject: [PATCH 0/3] crypto: sha - Implement export_core() and import_core()
Date: Mon, 1 Sep 2025 09:50:10 -0700 [thread overview]
Message-ID: <20250901165013.48649-1-ebiggers@kernel.org> (raw)
This series implements export_core() and import_core() in sha1.c,
sha256.c, and sha512.c to fix some legacy drivers. Unfortunately, the
Crypto API partial block handling changes that went into v6.16 made some
legacy drivers start depending on the presence of these methods.
This series is targeting libcrypto-fixes.
Eric Biggers (3):
crypto: sha1 - Implement export_core() and import_core()
crypto: sha256 - Implement export_core() and import_core()
crypto: sha512 - Implement export_core() and import_core()
crypto/sha1.c | 39 +++++++++++++++++++++++++++
crypto/sha256.c | 71 +++++++++++++++++++++++++++++++++++++++++++++++++
crypto/sha512.c | 71 +++++++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 181 insertions(+)
base-commit: b320789d6883cc00ac78ce83bccbfe7ed58afcf0
--
2.50.1
next reply other threads:[~2025-09-01 16:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 16:50 Eric Biggers [this message]
2025-09-01 16:50 ` [PATCH 1/3] crypto: sha1 - Implement export_core() and import_core() Eric Biggers
2025-09-02 8:23 ` Ovidiu Panait
2025-09-01 16:50 ` [PATCH 2/3] crypto: sha256 " Eric Biggers
2025-09-02 8:28 ` Ovidiu Panait
2025-09-01 16:50 ` [PATCH 3/3] crypto: sha512 " Eric Biggers
2025-09-02 8:36 ` Ovidiu Panait
2025-09-02 15:09 ` [PATCH 0/3] crypto: sha " Giovanni Cabiddu
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=20250901165013.48649-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=giovanni.cabiddu@intel.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ovidiu.panait.oss@gmail.com \
--cc=qat-linux@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.