[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <202511241115.BAFD2FC@keescook>
Date: Mon, 24 Nov 2025 11:17:02 -0800
From: Kees Cook <kees@...nel.org>
To: Eric Biggers <ebiggers@...nel.org>
Cc: "Jason A. Donenfeld" <Jason@...c4.com>,
Ard Biesheuvel <ardb@...nel.org>, linux-crypto@...r.kernel.org,
linux-kernel@...r.kernel.org,
Herbert Xu <herbert@...dor.apana.org.au>,
linux-hardening@...r.kernel.org
Subject: Re: [PATCH 0/6] lib/crypto: More at_least decorations
On Sun, Nov 23, 2025 at 12:54:31PM -0800, Eric Biggers wrote:
> Oh, there's actually a difference between const and non-const
> parameters. A const parameter gives -Wstringop-overread, while a
> non-const one gives -Wstringop-overflow. Only the latter is disabled.
FWIW, I'm hoping we can make the last bit of progress needed to get
-Warray-bounds and -Wstringop-overflow enabled globally after this
patch helps us track down any stragglers:
https://lore.kernel.org/lkml/20251121184342.it.626-kees@kernel.org/
-Kees
--
Kees Cook
Powered by blists - more mailing lists