From: Kees Cook <kees@kernel.org>
To: Will Deacon <will@kernel.org>
Cc: cki-project@redhat.com, catalin.marinas@arm.com,
linux-arm-kernel@lists.infradead.org, akpm@linux-foundation.org,
masahiroy@kernel.org
Subject: Re: ❌ FAIL: Test report for for-kernelci (6.14.0-rc1, upstream-arm-next, 2014c95a)
Date: Tue, 4 Feb 2025 06:40:25 -0800 [thread overview]
Message-ID: <202502040638.5EF4863D8@keescook> (raw)
In-Reply-To: <20250204111552.GA893@willie-the-truck>
On Tue, Feb 04, 2025 at 11:15:53AM +0000, Will Deacon wrote:
> [+Kees]
>
> On Tue, Feb 04, 2025 at 09:51:05AM -0000, cki-project@redhat.com wrote:
> > Hi, we tested your kernel and here are the results:
> >
> > Overall result: FAILED
> > Merge: OK
> > Compile: FAILED
> >
> >
> > Kernel information:
> > Commit message: Linux 6.14-rc1
> >
> > You can find all the details about the test run at
> > https://datawarehouse.cki-project.org/kcidb/checkouts/redhat:1654629441
>
> It looks like the build fails thanks to a rust panic:
>
> 00:00:10 EXPORTS rust/exports_helpers_generated.h
> 00:00:11 panicked at main.rs:52:36:
> 00:00:11 Unable to generate bindings: ClangDiagnostic("error: unknown argument: '-fzero-init-padding-bits=all'\n")
> 00:00:11 make[4]: *** [rust/Makefile:332: rust/bindings/bindings_helpers_generated.rs] Error 101
>
> Presumably introduced by dce4aab8441d ("kbuild: Use
> -fzero-init-padding-bits=all"). I'm guessing that option isn't supposed
> to propagate to .rs sources?
How is that getting passed to Clang? That's a GCC-only option, with
"cc-option":
+KBUILD_CFLAGS += $(call cc-option,-fzero-init-padding-bits=all)
I will take a look...
-Kees
--
Kees Cook
next prev parent reply other threads:[~2025-02-04 14:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 9:51 ❌ FAIL: Test report for for-kernelci (6.14.0-rc1, upstream-arm-next, 2014c95a) cki-project
2025-02-04 11:15 ` Will Deacon
2025-02-04 14:40 ` Kees Cook [this message]
2025-02-04 20:10 ` Nathan Chancellor
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=202502040638.5EF4863D8@keescook \
--to=kees@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=cki-project@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=masahiroy@kernel.org \
--cc=will@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).