From: Giovanni Cabiddu <giovanni.cabiddu@intel.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: <linux-crypto@vger.kernel.org>, <qat-linux@intel.com>,
<linux-kernel@vger.kernel.org>, Ard Biesheuvel <ardb@kernel.org>,
"Jason A . Donenfeld" <Jason@zx2c4.com>
Subject: Re: [PATCH] crypto: qat: Use library to prepare HMAC keys
Date: Mon, 1 Sep 2025 17:04:37 +0100 [thread overview]
Message-ID: <aLXEFW/YF4LyukGp@gcabiddu-mobl.ger.corp.intel.com> (raw)
In-Reply-To: <20250831205457.36143-1-ebiggers@kernel.org>
On Sun, Aug 31, 2025 at 01:54:57PM -0700, Eric Biggers wrote:
> Reimplementing the sha1, sha256, and sha512 crypto_shash algorithms on
> top of the library APIs caused the recently-added function
> crypto_shash_export_core() to no longer be supported. Meanwhile, the
> QAT driver was updated to use crypto_shash_export_core(). But it's not
> actually necessary. Instead, just do the HMAC key preparation using the
> library functions instead of crypto_shash. This fixes the QAT driver
> and greatly simplifies the code. Additional benefits include stronger
> typing, and improved performance due to reduced overhead.
>
> Reported-by: Giovanni Cabiddu <giovanni.cabiddu@intel.com>
> Closes: https://lore.kernel.org/r/aLSnCc9Ws5L9y+8X@gcabiddu-mobl.ger.corp.intel.com
> Fixes: ccafe2821cfa ("crypto: qat - Use crypto_shash_export_core")
> Fixes: 8bc79ab67d78 ("crypto: sha1 - Wrap library and add HMAC support")
> Fixes: e0cd37169103 ("crypto: sha256 - Wrap library and add HMAC support")
> Fixes: 469acaa12502 ("crypto: sha512 - Replace sha512_generic with wrapper around SHA-512 library")
> Signed-off-by: Eric Biggers <ebiggers@kernel.org>
> ---
Thanks.
One NIT on the headline, for consistency with the other patches:
"crypto: qat -".
Acked-by: Giovanni Cabiddu <giovanni.cabiddu@intel.com>
Regards,
--
Giovanni
prev parent reply other threads:[~2025-09-01 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-31 20:54 Eric Biggers
2025-09-01 16:04 ` Giovanni Cabiddu [this message]
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=aLXEFW/YF4LyukGp@gcabiddu-mobl.ger.corp.intel.com \
--to=giovanni.cabiddu@intel.com \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=ebiggers@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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®