From: "Nikunj A. Dadhania" <nikunj@amd.com>
To: Borislav Petkov <bp@alien8.de>,
Eric Biggers <ebiggers@kernel.org>,
"Tom Lendacky" <thomas.lendacky@amd.com>,
Michael Roth <michael.roth@amd.com>
Cc: linux-crypto@vger.kernel.org, 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, "Carlos López" <clopez@suse.de>,
"Alexey Kardashevskiy" <aik@amd.com>
Subject: Re: [PATCH 0/3] Remove old AES-GCM library
Date: Thu, 23 Jul 2026 11:44:17 +0530 [thread overview]
Message-ID: <a9b0b8eb-e43e-4ae1-9ba2-25dd7955be63@amd.com> (raw)
In-Reply-To: <20260722160347.GBamDp48Gyb1jYXKTf@fat_crate.local>
On 7/22/2026 9:33 PM, Borislav Petkov wrote:
> On Tue, Jul 21, 2026 at 07:53:35PM -0700, Eric Biggers wrote:
>> 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.
>
> Fine with me as long as the additionally added AMD folks can verify everything
> still works with their SNP guest setups.
Tested with a SecureTSC-enabled SNP guest. SecureTSC guests rely on the SNP
guest messaging API which uses AES-GCM library, so this exercises the new
library code through that path. No issues found.
Tested-by: Nikunj A Dadhania <nikunj@amd.com>
next prev parent reply other threads:[~2026-07-23 6:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 2:53 [PATCH 0/3] Remove old AES-GCM library Eric Biggers
2026-07-22 2:53 ` [PATCH 1/3] x86/sev: Use new " Eric Biggers
2026-07-22 2:53 ` [PATCH 2/3] x86/sev: Remove obsolete virtual address check Eric Biggers
2026-07-22 10:01 ` Ard Biesheuvel
2026-07-22 15:16 ` Eric Biggers
2026-07-22 2:53 ` [PATCH 3/3] lib/crypto: aesgcm: Remove old AES-GCM library Eric Biggers
2026-07-22 9:59 ` [PATCH 0/3] " Ard Biesheuvel
2026-07-22 16:03 ` Borislav Petkov
2026-07-23 6:14 ` Nikunj A. Dadhania [this message]
2026-07-30 1:37 ` 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=a9b0b8eb-e43e-4ae1-9ba2-25dd7955be63@amd.com \
--to=nikunj@amd.com \
--cc=Jason@zx2c4.com \
--cc=aik@amd.com \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=clopez@suse.de \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.roth@amd.com \
--cc=thomas.lendacky@amd.com \
--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