From: Eric Biggers <ebiggers@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: linux-crypto@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
Antoine Tenart <atenart@kernel.org>
Subject: Re: [PATCH] crypto: inside-secure - remove crc32 support
Date: Sun, 8 Jun 2025 16:41:19 -0700 [thread overview]
Message-ID: <20250608234119.GC1259@sol> (raw)
In-Reply-To: <20250531204244.24648-1-ebiggers@kernel.org>
On Sat, May 31, 2025 at 01:42:44PM -0700, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> The crc32 acceleration in the inside-secure driver is accessible only as
> an asynchronous hash. However, there seems to be no corresponding user
> of crc32 in the kernel that supports asynchronous hashes. Therefore,
> this code seems to be unused.
>
> The patch that added this code provided no justification for its
> inclusion. All devicetree bindings for this accelerator are for arm64;
> arm64 CPUs often have CRC or PMULL instructions, which already
> accelerate crc32 very well. And these actually work with the crc32
> users in the kernel, unlike this driver which doesn't.
>
> Remove this unnecessary code.
>
> Cc: Antoine Tenart <atenart@kernel.org>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> ---
>
> I'm planning to take this patch via the crc tree.
>
> drivers/crypto/inside-secure/safexcel.c | 1 -
> drivers/crypto/inside-secure/safexcel.h | 1 -
> drivers/crypto/inside-secure/safexcel_hash.c | 92 +-------------------
> 3 files changed, 2 insertions(+), 92 deletions(-)
Applied to https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git/log/?h=crc-next
- Eric
prev parent reply other threads:[~2025-06-08 23:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-31 20:42 [PATCH] crypto: inside-secure - remove crc32 support Eric Biggers
2025-06-01 9:03 ` Ard Biesheuvel
2025-06-08 23:41 ` Eric Biggers [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=20250608234119.GC1259@sol \
--to=ebiggers@kernel.org \
--cc=ardb@kernel.org \
--cc=atenart@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).