From: David Laight <david.laight.linux@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Kees Cook <kees@kernel.org>, Guenter Roeck <linux@roeck-us.net>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH] gcc-15: acpi: sprinkle random '__nonstring' crumbles around
Date: Sun, 27 Apr 2025 12:24:02 +0100 [thread overview]
Message-ID: <20250427122402.4f4fbfa8@pumpkin> (raw)
In-Reply-To: <CAHk-=whryuuKnd_5w6169EjfRr_f+t5BRmKt+qfjALFzfKQNvQ@mail.gmail.com>
On Sun, 20 Apr 2025 21:33:19 -0700
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Sun, 20 Apr 2025 at 18:52, Kees Cook <kees@kernel.org> wrote:
> >
> > Can you please revert this mess and use what has already been planned
> > for this warning? It is, once again, really frustrating when you update
> > to unreleased compiler versions. :(
>
> Ehh. Kees, that's the compiler in F42.
>
> Really. It's not some "unreleased compiler version".
Would it make sens to disable the warning on versions of gcc 15 that don't
contain all the 'fixes'?
After all they are compile time checks so only need to be detected
by one person doing a build - not everyone.
David
>
> It's the main compiler in one of the biggest Linux distributions, out now.
>
> Why do you think I made the change? Because the kernel DID NOT BUILD
> without those changes.
>
> So no. This was not some kind of "solved problem". Quite the reverse.
>
> Linus
>
prev parent reply other threads:[~2025-04-27 11:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 0:35 [PATCH] gcc-15: acpi: sprinkle random '__nonstring' crumbles around Guenter Roeck
2025-04-21 1:52 ` Kees Cook
2025-04-21 4:33 ` Linus Torvalds
2025-04-21 16:39 ` Kees Cook
2025-04-21 16:50 ` Linus Torvalds
2025-04-27 11:24 ` David Laight [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=20250427122402.4f4fbfa8@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=kees@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=torvalds@linux-foundation.org \
/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