From: Eric Biggers <ebiggers@kernel.org>
To: linux-crypto@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, "Ard Biesheuvel" <ardb@kernel.org>,
"Jason A . Donenfeld" <Jason@zx2c4.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
x86@kernel.org, "Borislav Petkov" <bp@alien8.de>,
"Carlos López" <clopez@suse.de>,
"Alexey Kardashevskiy" <aik@amd.com>,
"Eric Biggers" <ebiggers@kernel.org>
Subject: [PATCH 0/3] Remove old AES-GCM library
Date: Tue, 21 Jul 2026 19:53:35 -0700 [thread overview]
Message-ID: <20260722025338.33354-1-ebiggers@kernel.org> (raw)
The old AES-GCM library code is being replaced as part of an overhaul
that is adding support for all the common AES encryption modes with
consistent conventions
(https://lore.kernel.org/linux-crypto/20260715221153.246410-1-ebiggers@kernel.org/).
The SEV code is the only user of the old API. Update it to use the new
API instead. Then remove the old API.
This applies to libcrypto-next. If possible I'd like to take this
through libcrypto-next for 7.3. Acks are appreciated.
Eric Biggers (3):
x86/sev: Use new AES-GCM library
x86/sev: Remove obsolete virtual address check
lib/crypto: aesgcm: Remove old AES-GCM library
arch/x86/Kconfig | 2 +-
arch/x86/coco/sev/core.c | 53 +-
arch/x86/include/asm/sev.h | 2 +-
drivers/virt/coco/sev-guest/sev-guest.c | 7 +-
include/crypto/gcm.h | 21 -
lib/crypto/Kconfig | 6 -
lib/crypto/Makefile | 3 -
lib/crypto/aesgcm.c | 721 ------------------------
8 files changed, 26 insertions(+), 789 deletions(-)
delete mode 100644 lib/crypto/aesgcm.c
base-commit: e4f23159c8d09b6b15d47f2c95e0a3e7c62f52a2
--
2.55.0
next reply other threads:[~2026-07-22 2:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 2:53 Eric Biggers [this message]
2026-07-22 2:53 ` [PATCH 1/3] x86/sev: Use new AES-GCM library Eric Biggers
2026-07-22 2:53 ` [PATCH 2/3] x86/sev: Remove obsolete virtual address check Eric Biggers
2026-07-22 2:53 ` [PATCH 3/3] lib/crypto: aesgcm: Remove old AES-GCM library Eric Biggers
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=20260722025338.33354-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=Jason@zx2c4.com \
--cc=aik@amd.com \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=clopez@suse.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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