public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Herbert Xu <herbert@gondor.apana.org.au>,
	"Jason A . Donenfeld " <Jason@zx2c4.com>,
	"Justin M. Forbes" <jforbes@fedoraproject.org>
Cc: linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org
Subject: Re: [PATCH v3 2/3] crypto: lib - move __crypto_xor into utils
Date: Thu, 25 Aug 2022 21:44:38 -0700	[thread overview]
Message-ID: <YwhPtnL6yVG0K2Lo@sol.localdomain> (raw)
In-Reply-To: <20220725183636.97326-3-ebiggers@kernel.org>

Herbert, Jason, and Justin:

On Mon, Jul 25, 2022 at 11:36:35AM -0700, Eric Biggers wrote:
> diff --git a/lib/crypto/Kconfig b/lib/crypto/Kconfig
> index b09d9d6546cbc3..7e9683e9f5c636 100644
> --- a/lib/crypto/Kconfig
> +++ b/lib/crypto/Kconfig
> @@ -36,7 +36,7 @@ config CRYPTO_ARCH_HAVE_LIB_CHACHA
>  
>  config CRYPTO_LIB_CHACHA_GENERIC
>  	tristate
> -	select XOR_BLOCKS
> +	select CRYPTO_LIB_UTILS
>  	help
>  	  This symbol can be depended upon by arch implementations of the
>  	  ChaCha library interface that require the generic code as a

Just a heads up; the unnecessary selection of XOR_BLOCKS here (which got
backported to v5.10.120 and v5.15.45 by "lib/crypto: add prompts back to crypto
libraries") can be considered an actual bug, as it increases boot time on
systems that didn't have it selected before.  This is because the code enabled
by XOR_BLOCKS (crypto/xor.c) runs a benchmark, which takes some time.  It
doesn't take *that* long, but it got noticed as a regression nonetheless, and it
needs to be fixed.  My patch series happens to have fixed this, but I didn't
have it mind that it was a real bug fix.

Herbert, any chance that you could send my patch series to Linus without waiting
for the next merge window, so that it can be backported?

- Eric

  parent reply	other threads:[~2022-08-26  4:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-25 18:36 [PATCH v3 0/3] crypto: lib - create utils module Eric Biggers
2022-07-25 18:36 ` [PATCH v3 1/3] crypto: lib - create utils module and move __crypto_memneq into it Eric Biggers
2022-07-25 22:10   ` Jason A. Donenfeld
2022-07-25 18:36 ` [PATCH v3 2/3] crypto: lib - move __crypto_xor into utils Eric Biggers
2022-07-25 22:09   ` Jason A. Donenfeld
2022-07-26  1:00     ` Eric Biggers
2022-07-26 13:46     ` Ard Biesheuvel
2022-08-26  4:44   ` Eric Biggers [this message]
2022-08-26  4:46     ` Herbert Xu
2022-08-26  4:48       ` Eric Biggers
2022-08-26  4:52         ` Herbert Xu
2022-08-26  5:07           ` Eric Biggers
2022-07-25 18:36 ` [PATCH v3 3/3] crypto: lib - remove __HAVE_ARCH_CRYPTO_MEMNEQ Eric Biggers
2022-07-25 22:07   ` Jason A. Donenfeld
2022-07-26  0:51     ` Eric Biggers
2022-08-19 10:59 ` [PATCH v3 0/3] crypto: lib - create utils module 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=YwhPtnL6yVG0K2Lo@sol.localdomain \
    --to=ebiggers@kernel.org \
    --cc=Jason@zx2c4.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=jforbes@fedoraproject.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.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