[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y4lxu+6BQJ5uVhCg@sol.localdomain>
Date: Thu, 1 Dec 2022 19:32:11 -0800
From: Eric Biggers <ebiggers@...nel.org>
To: Kees Cook <keescook@...omium.org>
Cc: Horia Geantă <horia.geanta@....com>,
Herbert Xu <herbert@...dor.apana.org.au>,
Pankaj Gupta <pankaj.gupta@....com>,
Gaurav Jain <gaurav.jain@....com>,
"David S. Miller" <davem@...emloft.net>,
linux-crypto@...r.kernel.org, kernel test robot <lkp@...el.com>,
Anders Roxell <anders.roxell@...aro.org>,
linux-kernel@...r.kernel.org, linux-hardening@...r.kernel.org
Subject: Re: [PATCH v2] crypto/caam: Avoid GCC constprop bug warning
On Thu, Dec 01, 2022 at 07:23:49PM -0800, Kees Cook wrote:
> I think it's a dumb
> limitation, given that "zero size to/from NULL" is perfectly valid.
No, that is undefined behavior. Which is presumably the reason for the nonnull
annotation. Anyway, it is silly, which is why I'd hope that someone would have
added an option to disable this C standard bug by now...
- Eric
Powered by blists - more mailing lists