From: Herbert Xu <herbert@gondor.apana.org.au>
To: Linus Torvalds <torvalds@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: [GIT PULL] Crypto Fixes for 7.1
Date: Tue, 21 Apr 2026 16:53:22 +0800 [thread overview]
Message-ID: <aec7Aj9lhK3YGZjF@gondor.apana.org.au> (raw)
Hi Linus:
The following changes since commit aec2f682d47c54ef434b2d440992626d80b1ebdc:
Merge tag 'v7.1-p1' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6 (2026-04-15 15:22:26 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6 tags/v7.1-p2
for you to fetch changes up to 3bfbf5f0a99c991769ec562721285df7ab69240b:
crypto: krb5enc - fix async decrypt skipping hash verification (2026-04-20 16:18:58 +0800)
----------------------------------------------------------------
This push contains the following changes:
- Fix IPsec ESN regression in authencesn.
- Fix hmac setkey failure in eip93.
- Guard against IV changing in algif_aead.
- Fix async completion handling in krb5enc.
- Fix fallback async completion in acomp.
- Fix handling of MAY_BACKLOG requests in pcrypt.
- Fix issues with firmware-returned values in ccp.
----------------------------------------------------------------
Aleksander Jan Bajkowski (1):
crypto: eip93 - fix hmac setkey algo selection
Douya Le (1):
crypto: algif_aead - snapshot IV for async AEAD requests
Dudu Lu (1):
crypto: krb5enc - fix async decrypt skipping hash verification
Giovanni Cabiddu (1):
crypto: acomp - fix wrong pointer stored by acomp_save_req()
Herbert Xu (2):
crypto: authencesn - Fix src offset when decrypting in-place
crypto: pcrypt - Fix handling of MAY_BACKLOG requests
Paul Moses (1):
crypto: ccp - copy IV using skcipher ivsize
Sean Christopherson (3):
crypto: ccp: Don't attempt to copy CSR to userspace if PSP command failed
crypto: ccp: Don't attempt to copy PDH cert to userspace if PSP command failed
crypto: ccp: Don't attempt to copy ID to userspace if PSP command failed
T Pratham (1):
crypto: sa2ul - Fix AEAD fallback algorithm names
crypto/acompress.c | 8 ++--
crypto/algif_aead.c | 10 ++++-
crypto/authencesn.c | 6 ++-
crypto/krb5enc.c | 52 ++++++++++++++---------
crypto/pcrypt.c | 7 ++-
drivers/crypto/ccp/ccp-crypto-aes.c | 7 ++-
drivers/crypto/ccp/sev-dev.c | 19 ++++++++-
drivers/crypto/inside-secure/eip93/eip93-common.c | 2 +-
drivers/crypto/sa2ul.c | 4 +-
9 files changed, 76 insertions(+), 39 deletions(-)
Thanks,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next reply other threads:[~2026-04-21 8:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 8:53 Herbert Xu [this message]
2026-04-21 16:25 ` [GIT PULL] Crypto Fixes for 7.1 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2026-05-02 4:40 Herbert Xu
2026-05-02 20:27 ` pr-tracker-bot
2026-05-15 9:37 Herbert Xu
2026-05-15 20:10 ` pr-tracker-bot
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=aec7Aj9lhK3YGZjF@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=davem@davemloft.net \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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