From: Kees Cook <kees@kernel.org>
To: Shyam Saini <shyamsaini@linux.microsoft.com>
Cc: masahiroy@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] init/Kconfig: conditionalize GCC10_NO_ARRAY_BOUNDS
Date: Fri, 4 Apr 2025 10:29:29 -0700 [thread overview]
Message-ID: <202504041028.6E6C6268@keescook> (raw)
In-Reply-To: <20250327183559.3339185-1-shyamsaini@linux.microsoft.com>
On Thu, Mar 27, 2025 at 11:35:59AM -0700, Shyam Saini wrote:
> do you have any reviews for this patch?
It's a redundant change since CC_IS_GCC is checked later:
config GCC10_NO_ARRAY_BOUNDS
def_bool y
config CC_NO_ARRAY_BOUNDS
bool
default y if CC_IS_GCC && GCC_VERSION >= 90000 && GCC10_NO_ARRAY_BOUNDS
If you wanted to make this change, then it would make sense to drop it
from CC_NO_ARRAY_BOUNDS at the same time.
-Kees
--
Kees Cook
prev parent reply other threads:[~2025-04-04 17:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 7:25 [PATCH] init/Kconfig: conditionalize GCC10_NO_ARRAY_BOUNDS Shyam Saini
2025-02-11 22:10 ` Shyam Saini
2025-03-27 18:35 ` Shyam Saini
2025-04-04 17:29 ` Kees Cook [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=202504041028.6E6C6268@keescook \
--to=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=shyamsaini@linux.microsoft.com \
/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