From: "Günther Noack" <gnoack3000@gmail.com>
To: WangYuli <wangyuli@uniontech.com>
Cc: mic@digikod.net, gnoack@google.com, paul@paul-moore.com,
jmorris@namei.org, serge@hallyn.com, kees@kernel.org,
masahiroy@kernel.org, nathan@kernel.org, nicolas@fjasle.eu,
linux-security-module@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-hardening@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [Bug Report] A compilation failure occurs when landlock and RANDSTRUCT are combined with GCC 14.2.0.
Date: Thu, 10 Apr 2025 17:33:21 +0200 [thread overview]
Message-ID: <20250410.926dbc57c00b@gnoack.org> (raw)
In-Reply-To: <337D5D4887277B27+3c677db3-a8b9-47f0-93a4-7809355f1381@uniontech.com>
Hello!
On Thu, Apr 10, 2025 at 04:11:15PM +0800, WangYuli wrote:
> [ Compilation failure log: ]
>
> *** WARNING *** there are active plugins, do not report this as a bug unless
> you can reproduce it without enabling an
> y plugins.
> Event | Plugins
> PLUGIN_FINISH_TYPE | randomize_layout_plugin
> PLUGIN_FINISH_DECL | randomize_layout_plugin
> PLUGIN_ATTRIBUTES | latent_entropy_plugin
> randomize_layout_plugin
> PLUGIN_START_UNIT | latent_entropy_plugin stackleak_plugin
> PLUGIN_ALL_IPA_PASSES_START | randomize_layout_plugin
> security/landlock/fs.c:In function ‘hook_file_ioctl_common’:
> security/landlock/fs.c:1745:61:internal compiler error: in
> count_type_elements, at expr.cc:7075
> 1745 | .u.op = &(struct lsm_ioctlop_audit) {
> | ^
> 0x7f27fa6bdca7 __libc_start_call_main
> ../sysdeps/nptl/libc_start_call_main.h:58
> 0x7f27fa6bdd64 __libc_start_main_impl
> ../csu/libc-start.c:360
> Please submit a full bug report, with preprocessed source (by using
> -freport-bug).
> Please include the complete backtrace with any bug report.
> See <file:///usr/share/doc/gcc-14/README.Bugs> for instructions.
> make[4]: *** [scripts/Makefile.build:203: security/landlock/fs.o] Error 1
> make[3]: *** [scripts/Makefile.build:461: security/landlock] Error 2
> make[2]: *** [scripts/Makefile.build:461: security] Error 2
Thank you for the report!
This is in my understanding a duplicate of the discussion in
https://lore.kernel.org/all/20250407-kbuild-disable-gcc-plugins-v1-1-5d46ae583f5e@kernel.org/
–Günther
next prev parent reply other threads:[~2025-04-10 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 8:11 [Bug Report] A compilation failure occurs when landlock and RANDSTRUCT are combined with GCC 14.2.0 WangYuli
2025-04-10 15:33 ` Günther Noack [this message]
2025-04-10 17:05 ` Mickaël Salaün
2025-04-11 2:50 ` WangYuli
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=20250410.926dbc57c00b@gnoack.org \
--to=gnoack3000@gmail.com \
--cc=gnoack@google.com \
--cc=jmorris@namei.org \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mic@digikod.net \
--cc=nathan@kernel.org \
--cc=nicolas@fjasle.eu \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=wangyuli@uniontech.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