Re: [PATCH] [v2] landlock: work around gcc-16 -Wuninitialized warning

On Wed, Sep 16, 2026, at 14:25, Mickaël Salaün wrote:

On Wed, Sep 16, 2026 at 10:49:47AM +0200, Sebastian Andrzej Siewior wrote:

quoted

On 2026-09-15 22:10:30 [+0200], Arnd Bergmann wrote:

quoted

Link: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110743
Link: https://lore.kernel.org/all/20260619082133.3504146-1-arnd@kernel.org/ (local)
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.

quoted

quoted

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?

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.

      Arnd