From: "Mickaël Salaün" <mic@digikod.net>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: "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>,
"Arnd Bergmann" <arnd@arndb.de>,
"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: Wed, 16 Sep 2026 14:25:41 +0200 [thread overview]
Message-ID: <20260916.shai0tha3IPa@digikod.net> (raw)
In-Reply-To: <20260916084947.6QDy8KZQ@linutronix.de>
On Wed, Sep 16, 2026 at 10:49:47AM +0200, Sebastian Andrzej Siewior wrote:
> On 2026-09-15 22:10:30 [+0200], Arnd Bergmann wrote:
> > Link: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110743
> > Link: https://lore.kernel.org/all/20260619082133.3504146-1-arnd@kernel.org/
> > Fixes: a260c0055665 ("landlock: Add a place for flags to layer rules")
> > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> > ---
> > v2: rebased to linux-next-20260914
> >
> > I originally sent this in June, but got no reply and this still
> > happens with gcc-16.2, which is the latest stable release.
Thanks Arnd, I missed it. It's in my -next branch now.
> >
> > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>
> This looks reasonable. I don't see this with gcc-16.2 and the referenced
> gcc bug has it as fixed.
If GCC is fixed now, should we keep this work around?
>
> Sebastian
>
next prev parent reply other threads:[~2026-09-16 12:25 UTC|newest]
Thread overview: 5+ 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 [this message]
2026-09-16 21:06 ` Arnd Bergmann
2026-09-17 7:09 ` Sebastian Andrzej Siewior
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=20260916.shai0tha3IPa@digikod.net \
--to=mic@digikod.net \
--cc=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=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®