public inbox for linux-crypto@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: linux-crypto@vger.kernel.org
Cc: x86@kernel.org
Subject: Re: [PATCH] crypto: x86/aes-gcm - simplify GCM hash subkey derivation
Date: Sat, 20 Apr 2024 11:19:42 -0700	[thread overview]
Message-ID: <20240420181942.GA786@quark.localdomain> (raw)
In-Reply-To: <20240420060037.26014-1-ebiggers@kernel.org>

On Fri, Apr 19, 2024 at 11:00:37PM -0700, Eric Biggers wrote:
> +	aes_encrypt(aes_key, hash_subkey, page_address(ZERO_PAGE(0)));

Actually, page_address(ZERO_PAGE(0)) expands into a surprisingly large number of
instructions.  Using empty_zero_page directly would avoid this, but there's
little precedent for doing that.  For now, I think just using something like
'static const u8 zeroes[16]' is the way to go for small buffers like this.

- Eric

  reply	other threads:[~2024-04-20 18:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-20  6:00 [PATCH] crypto: x86/aes-gcm - simplify GCM hash subkey derivation Eric Biggers
2024-04-20 18:19 ` Eric Biggers [this message]
2024-04-26  9:39   ` Herbert Xu

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=20240420181942.GA786@quark.localdomain \
    --to=ebiggers@kernel.org \
    --cc=linux-crypto@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