mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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.0
Date: Fri, 3 Apr 2026 08:24:05 +0800	[thread overview]
Message-ID: <ac8IpdQbWxiGuq0E@gondor.apana.org.au> (raw)

Hi Linus:

The following changes since commit 5c52607c43c397b79a9852ce33fc61de58c3645c:

  crypto: ccp - Fix leaking the same page twice (2026-03-14 14:01:37 +0900)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6 tags/v7.0-p4

for you to fetch changes up to e02494114ebf7c8b42777c6cd6982f113bfdbec7:

  crypto: authencesn - Do not place hiseq at end of dst for out-of-place decryption (2026-03-31 17:11:48 +0900)

----------------------------------------------------------------
This push contains the following changes:

- Add missing async markers to tegra.
- Fix long hmac key DMA handling in caam.
- Fix spurious ENOSPC errors in deflate.
- Fix SG chaining in af_alg.
- Do not use in-place process in algif_aead.
- Fix out-of-place destination overflow in authencesn.
----------------------------------------------------------------

Eric Biggers (1):
      crypto: tegra - Add missing CRYPTO_ALG_ASYNC

Herbert Xu (2):
      crypto: algif_aead - Revert to operating out-of-place
      crypto: authencesn - Do not place hiseq at end of dst for out-of-place decryption

Horia Geantă (2):
      crypto: caam - fix DMA corruption on long hmac keys
      crypto: caam - fix overflow on long hmac keys

Mikulas Patocka (1):
      crypto: deflate - fix spurious -ENOSPC

Norbert Szetei (1):
      crypto: af-alg - fix NULL pointer dereference in scatterwalk

 crypto/af_alg.c                      |  53 +++++--------------
 crypto/algif_aead.c                  | 100 +++++++----------------------------
 crypto/algif_skcipher.c              |   6 +--
 crypto/authencesn.c                  |  50 +++++++++++-------
 crypto/deflate.c                     |  11 ++--
 drivers/crypto/caam/caamalg_qi2.c    |   3 +-
 drivers/crypto/caam/caamhash.c       |   3 +-
 drivers/crypto/tegra/tegra-se-aes.c  |  11 ++--
 drivers/crypto/tegra/tegra-se-hash.c |  30 ++++++-----
 include/crypto/if_alg.h              |   5 +-
 10 files changed, 102 insertions(+), 170 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

             reply	other threads:[~2026-04-03  0:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-03  0:24 Herbert Xu [this message]
2026-04-03  4:12 ` pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2026-04-12  5:42 Herbert Xu
2026-04-12 17:45 ` pr-tracker-bot
2026-03-06  3:01 Herbert Xu
2026-03-06 18:38 ` pr-tracker-bot
2026-03-18  7:50 ` Herbert Xu
2026-03-18 17:00   ` 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=ac8IpdQbWxiGuq0E@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

all inboxes | Powered by JetHome®