From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: gregkh@linuxfoundation.org, kees@kernel.org, linux@roeck-us.net,
vbabka@suse.cz, stable-commits@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: Patch "gcc: disable -Warray-bounds for gcc-11 too" has been added to the 6.1-stable tree
Date: Thu, 12 Jan 2023 16:10:08 -0800 [thread overview]
Message-ID: <202301121559.AE5064D@keescook> (raw)
In-Reply-To: <CAHk-=wjq1jd4ht7RvB8HYDJFAH=dRQ+43-mj3LWMJReF4yu34Q@mail.gmail.com>
On Thu, Jan 12, 2023 at 05:22:53PM -0600, Linus Torvalds wrote:
> But right now it seems a matter of "just by luck, we don't hit it
> anywhere else", and I'm not interested in playing any more
> whack-a-mole with this broken compiler option.
Okay, understood.
FWIW, I've been tracking these and getting reproducers so they can
get worked on. A few got fixed for GCC 12, and but not enough to turn
-Warray-bounds on there. More were fixed in GCC 13. So far, I'm aware
of these 3 getting fixed since we started trying to enable
-Warray-bounds:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105679
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99578
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101419
I recently reported 1:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108306
And these 3 are likely related, but for options we don't yet enable,
but seem to be internal issues with the value range handling (usually
when a sanitizer of one kind or another is enabled):
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97490
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99673
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101778
The powerpc issue hasn't been reported yet. It's my intention to do so
once I can get it minimized.
--
Kees Cook
next prev parent reply other threads:[~2023-01-13 0:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <167352819915167@kroah.com>
2023-01-12 21:50 ` Patch "gcc: disable -Warray-bounds for gcc-11 too" has been added to the 6.1-stable tree Kees Cook
2023-01-12 23:22 ` Linus Torvalds
2023-01-13 0:10 ` Kees Cook [this message]
2023-01-14 0:36 ` Kees Cook
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=202301121559.AE5064D@keescook \
--to=keescook@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=stable-commits@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.