Re: [BUG] crypto: shash – crypto_shash_export_core() fails with -ENOSYS after libcrypto updates merge

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [BUG] crypto: shash – crypto_shash_export_core() fails with -ENOSYS after libcrypto updates merge
From: Eric Biggers <ebiggers@xxxxxxxxxx>
Date: Sun, 31 Aug 2025 13:54:27 -0700
Cc: herbert@xxxxxxxxxxxxxxxxxxx, linux-crypto@xxxxxxxxxxxxxxx, qat-linux@xxxxxxxxx
In-reply-to: <aLSnCc9Ws5L9y+8X@gcabiddu-mobl.ger.corp.intel.com>
References: <aLSnCc9Ws5L9y+8X@gcabiddu-mobl.ger.corp.intel.com>

On Sun, Aug 31, 2025 at 08:48:25PM +0100, Giovanni Cabiddu wrote:
> Should drivers like QAT switch to using the software library directly
> to export the SHA state?

Yes, that's the correct solution.  I'll send patches for the qat and
chelsio drivers.

- Eric

References:
- [BUG] crypto: shash – crypto_shash_export_core() fails with -ENOSYS after libcrypto updates merge
  - From: Giovanni Cabiddu

Prev by Date: [PATCH] crypto: chelsio: Use library to prepare HMAC keys
Next by Date: Re: [PATCH v1 13/36] mm/hugetlb: cleanup hugetlb_folio_init_tail_vmemmap()
Previous by thread: Re: [BUG] crypto: shash – crypto_shash_export_core() fails with -ENOSYS after libcrypto updates merge
Next by thread: Re: [PATCH v1 11/36] mm: limit folio/compound page sizes in problematic kernel configs
Index(es):
- Date
- Thread

[Index of Archives] [Kernel] [Gnu Classpath] [Gnu Crypto] [DM Crypt] [Netfilter] [Bugtraq]

Powered by Linux