From: "Arnd Bergmann" <arnd@arndb.de>
To: "Sebastian Andrzej Siewior" <bigeasy@linutronix.de>
Cc: "Mickaël Salaün" <mic@digikod.net>,
"Arnd Bergmann" <arnd@kernel.org>,
"Paul Moore" <paul@paul-moore.com>,
"James Morris" <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
"Tingmao Wang" <m@maowtm.org>,
"Justin Suess" <utilityemal77@gmail.com>,
"Günther Noack" <gnoack@google.com>,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [v2] landlock: work around gcc-16 -Wuninitialized warning
Date: Thu, 17 Sep 2026 13:36:15 +0200 [thread overview]
Message-ID: <95e794f6-6ec4-4b3e-bfa8-7edae0ac898e@app.fastmail.com> (raw)
In-Reply-To: <20260917104544.3trW9Jq1@linutronix.de>
On Thu, Sep 17, 2026, at 12:45, Sebastian Andrzej Siewior wrote:
> On 2026-09-17 12:26:17 [+0200], Arnd Bergmann wrote:
>> I checked again and found that this is a config that did produce
>> the issue a few weeks ago, but doesn't today for me.
>> I found a different config from this week and managed to reproduce
>> the problem on today's linux-next using both gcc-16.2 and gcc-17.0
>> from yesterday, so there is still a related issue that is not
>> fixed in gcc, even though one at least one of them was fixed.
>
> Confirmed. I see the warning on arm64 while x86-64 is quiet. The patch
> fixes the issue.
>
> You might need to update gcc bug tracker.
Correction: I noticed the failing gcc-17 binary was an old one,
the current snapshot does not produce the warning any more.
It does seem like the fix was not yet backported to older compilers,
and seeing that the final gcc-13.x was released, we will
continue to need the kernel workaround. I assume the compiler
fix will eventually make its way into the other stable branches.
Arnd
next prev parent reply other threads:[~2026-09-17 11:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 20:10 Arnd Bergmann
2026-09-16 8:49 ` Sebastian Andrzej Siewior
2026-09-16 12:25 ` Mickaël Salaün
2026-09-16 21:06 ` Arnd Bergmann
2026-09-17 7:09 ` Sebastian Andrzej Siewior
2026-09-17 10:26 ` Arnd Bergmann
2026-09-17 10:45 ` Sebastian Andrzej Siewior
2026-09-17 11:36 ` Arnd Bergmann [this message]
2026-09-18 13:55 ` Mickaël Salaün
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=95e794f6-6ec4-4b3e-bfa8-7edae0ac898e@app.fastmail.com \
--to=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=gnoack@google.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=m@maowtm.org \
--cc=mic@digikod.net \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=utilityemal77@gmail.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
all inboxes | Powered by JetHome®