llvm.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Thorsten Blum <thorsten.blum@linux.dev>
Cc: Eric Biggers <ebiggers@kernel.org>,
	"Jason A. Donenfeld" <Jason@zx2c4.com>,
	Ard Biesheuvel <ardb@kernel.org>,
	Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
	Bill Wendling <morbo@google.com>,
	Justin Stitt <justinstitt@google.com>,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
	llvm@lists.linux.dev
Subject: Re: [PATCH v2] lib/crypto: blake2b: Limit frame size workaround to GCC
Date: Sun, 23 Nov 2025 14:13:17 -0700	[thread overview]
Message-ID: <20251123211317.GA3667167@ax162> (raw)
In-Reply-To: <20251123182515.548471-3-thorsten.blum@linux.dev>

On Sun, Nov 23, 2025 at 07:25:17PM +0100, Thorsten Blum wrote:
> The GCC regression only affected i386 and has been fixed since GCC 12.2.
> However, modern GCC versions still generate large stack frames on other
> architectures (e.g., 3440 bytes for blake2b_compress_generic() on m68k
> with GCC 15.1.0). Clang handles these functions efficiently and should
> work fine with the default warning threshold.
> 
> Limit the frame size workaround to GCC only.
> 
> Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>

Since the below comments are mostly nits:

Reviewed-by: Nathan Chancellor <nathan@kernel.org>

> ---
> Changes in v2:
> - Restrict frame size workaround to GCC independent of its version or
>   the architecture
> - Update patch title and description
> - Link to v1: https://lore.kernel.org/lkml/20251122105530.441350-2-thorsten.blum@linux.dev/
> ---
>  lib/crypto/Makefile | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/lib/crypto/Makefile b/lib/crypto/Makefile
> index b5346cebbb55..95a48393ffb4 100644
> --- a/lib/crypto/Makefile
> +++ b/lib/crypto/Makefile
> @@ -33,7 +33,9 @@ obj-$(CONFIG_CRYPTO_LIB_GF128MUL)		+= gf128mul.o
>  
>  obj-$(CONFIG_CRYPTO_LIB_BLAKE2B) += libblake2b.o
>  libblake2b-y := blake2b.o
> +ifeq ($(CONFIG_CC_IS_GCC),y)

I tend to prefer

  ifdef CONFIG_CC_IS_GCC

when the symbol is bool since it is a little easier to understand.

It may be worth a comment about the warnings on other architectures to
help future travellers who may be tempted to remove this when the
fixed GCC version of that bug report becomes the minimum.

>  CFLAGS_blake2b.o := -Wframe-larger-than=4096 #  https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105930
> +endif # CONFIG_CC_IS_GCC

This conditional feels small enough that it does not need this marker
but I guess that is maintainer preference.

>  ifeq ($(CONFIG_CRYPTO_LIB_BLAKE2B_ARCH),y)
>  CFLAGS_blake2b.o += -I$(src)/$(SRCARCH)
>  libblake2b-$(CONFIG_ARM) += arm/blake2b-neon-core.o
> -- 
> 2.51.1
> 

      reply	other threads:[~2025-11-23 21:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-23 18:25 [PATCH v2] lib/crypto: blake2b: Limit frame size workaround to GCC Thorsten Blum
2025-11-23 21:13 ` Nathan Chancellor [this message]

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=20251123211317.GA3667167@ax162 \
    --to=nathan@kernel.org \
    --cc=Jason@zx2c4.com \
    --cc=ardb@kernel.org \
    --cc=ebiggers@kernel.org \
    --cc=justinstitt@google.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=morbo@google.com \
    --cc=nick.desaulniers+lkml@gmail.com \
    --cc=thorsten.blum@linux.dev \
    /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;
as well as URLs for NNTP newsgroup(s).