From: Arnd Bergmann <arnd@kernel.org>
To: "Mickaël Salaün" <mic@digikod.net>,
"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>
Cc: "Arnd Bergmann" <arnd@arndb.de>,
"Günther Noack" <gnoack@google.com>,
"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] [v2] landlock: work around gcc-16 -Wuninitialized warning
Date: Tue, 15 Sep 2026 22:10:30 +0200 [thread overview]
Message-ID: <20260915201036.3527935-1-arnd@kernel.org> (raw)
From: Arnd Bergmann <arnd@arndb.de>
gcc has a bug with -ftrivial-auto-var-init=pattern that produces a
warning for correct code that uses sparse bitfields:
security/landlock/fs.c: In function 'is_access_to_paths_allowed.isra':
security/landlock/fs.c:767:28: error: '_layer_masks_child1' is used uninitialized [-Werror=uninitialized]
767 | struct layer_masks _layer_masks_child1, _layer_masks_child2;
| ^~~~~~~~~~~~~~~~~~~
security/landlock/fs.c:767:28: note: '_layer_masks_child1' declared here
767 | struct layer_masks _layer_masks_child1, _layer_masks_child2;
| ^~~~~~~~~~~~~~~~~~~
security/landlock/fs.c: In function 'hook_unix_find':
security/landlock/fs.c:1649:28: error: 'layer_masks' is used uninitialized [-Werror=uninitialized]
1649 | struct layer_masks layer_masks;
| ^~~~~~~~~~~
security/landlock/fs.c:1649:28: note: 'layer_masks' declared here
1649 | struct layer_masks layer_masks;
| ^~~~~~~~~~~
To work around this, change the definition of struct layer_mask to
use an explictit padding field. This also avoids the extra attributes
for aligning the structure.
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.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
---
security/landlock/access.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/security/landlock/access.h b/security/landlock/access.h
index bbbb41f41147..f41ac3fc6476 100644
--- a/security/landlock/access.h
+++ b/security/landlock/access.h
@@ -81,6 +81,9 @@ struct layer_mask {
*/
access_mask_t quiet : 1;
#endif /* CONFIG_SECURITY_LANDLOCK_LOG */
+ access_mask_t __pad : ((sizeof(access_mask_t) * 8) -
+ LANDLOCK_NUM_ACCESS_MAX -
+ IS_ENABLED(CONFIG_SECURITY_LANDLOCK_LOG));
} __packed __aligned(sizeof(access_mask_t));
/*
--
2.53.0
next reply other threads:[~2026-09-15 20:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 20:10 Arnd Bergmann [this message]
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
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=20260915201036.3527935-1-arnd@kernel.org \
--to=arnd@kernel.org \
--cc=arnd@arndb.de \
--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®