From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Arnd Bergmann <arnd@arndb.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 09:09:15 +0200 [thread overview]
Message-ID: <20260917070915.Ix8TOn5Y@linutronix.de> (raw)
In-Reply-To: <57b5869d-7411-46e8-ade6-6d2a7fea02ac@app.fastmail.com>
On 2026-09-16 23:06:30 [+0200], Arnd Bergmann wrote:
> As far as I can tell, 16.2 is still affected, even though it should be
> fixed in HEAD. gcc-16.3 won't be released until spring 2027 though.
>
> It is possible that there are additional configuration options that
> have to be set just right to reproduce the issue. I've attached a
> configuration that triggered it for me this week.
This is from v7.2. I tried this and v7.3-rc3 and did not notice a
warning (other than unrelated stack size from drm). I did notice:
-CONFIG_CC_VERSION_TEXT="x86_64-linux-gcc (GCC) 16.2.0"
+CONFIG_CC_VERSION_TEXT="gcc (Debian 16.2.0-2) 16.2.0"
CONFIG_GCC_VERSION=160200
-CONFIG_AS_VERSION=20285426
+CONFIG_AS_VERSION=24700
-CONFIG_LD_VERSION=20285426
+CONFIG_LD_VERSION=24700
+CONFIG_CC_HAS_MARCH_NATIVE=y
which might be the culprit. There were other things, too, so the
oldconfig was not clean (such as missing CONFIG_VIRTUALIZATION).
> Arnd
Sebastian
next prev parent reply other threads:[~2026-09-17 7:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 20:10 [PATCH] [v2] landlock: work around gcc-16 -Wuninitialized warning 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 [this message]
2026-09-17 10:26 ` Arnd Bergmann
2026-09-17 10:45 ` Sebastian Andrzej Siewior
2026-09-17 11:36 ` Arnd Bergmann
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=20260917070915.Ix8TOn5Y@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--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 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.