From: "Arnd Bergmann" <arnd@arndb.de>
To: "Naresh Kamboju" <naresh.kamboju@linaro.org>,
"open list" <linux-kernel@vger.kernel.org>,
linux-hardening@vger.kernel.org, lkft-triage@lists.linaro.org,
"Linux Regressions" <regressions@lists.linux.dev>
Cc: "Kees Cook" <kees@kernel.org>,
"Dan Carpenter" <dan.carpenter@linaro.org>,
"Anders Roxell" <anders.roxell@linaro.org>,
"Benjamin Copeland" <benjamin.copeland@linaro.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
"Masahiro Yamada" <masahiroy@kernel.org>
Subject: Re: next-20250730 x86, s390, riscv gcc-8 hardening.config vmlinux symbol `.modinfo' required but not present
Date: Thu, 31 Jul 2025 15:39:12 +0200 [thread overview]
Message-ID: <86f6a314-8aa0-46c3-8984-784a07a302c3@app.fastmail.com> (raw)
In-Reply-To: <CA+G9fYv-c6D6tJKw9x05+U_VxrpTAQCKADTeYg4jsjaJkX+isw@mail.gmail.com>
On Thu, Jul 31, 2025, at 15:32, Naresh Kamboju wrote:
> Regressions while building x86, S390 and riscv64 with hardening.config on the
> Linux next-20250730 and next-20250731.
>
> Build pass with gcc-13 with hardening.config fails with gcc-8
>
> Regression Analysis:
> - New regression? Yes
> - Reproducibility? Yes
>
> First seen on the next-20250730
> Good: next-20250729
> Bad: next-20250730
>
> Build regression: next-20250730 x86 gcc-8 hardening.config vmlinux
> symbol `.modinfo' required but not present
> Build regression: next-20250730 S390 gcc-8 hardening.config vmlinux
> symbol `.modinfo' required but not present
> Build regression: next-20250730 riscv64 gcc-8 hardening.config vmlinux
> symbol `__rela_dyn_end' required but not present
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
My guess is that this is caused by 94564d1bb059 ("kbuild: keep .modinfo
section in vmlinux.unstripped")
See also
https://lore.kernel.org/all/202507310505.tEYm1za7-lkp@intel.com/
https://lore.kernel.org/all/20250728135753.432695A72-agordeev@linux.ibm.com/
Reverting 94564d1bb059 solved the problem for me on arm64.
Arnd
prev parent reply other threads:[~2025-07-31 13:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 13:32 Naresh Kamboju
2025-07-31 13:39 ` Arnd Bergmann [this message]
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=86f6a314-8aa0-46c3-8984-784a07a302c3@app.fastmail.com \
--to=arnd@arndb.de \
--cc=anders.roxell@linaro.org \
--cc=benjamin.copeland@linaro.org \
--cc=dan.carpenter@linaro.org \
--cc=gustavoars@kernel.org \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=masahiroy@kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=regressions@lists.linux.dev \
/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®