linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Kees Cook <kees@kernel.org>
Cc: Will Deacon <will@kernel.org>,
	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 13:10:19 -0700	[thread overview]
Message-ID: <20250204201019.GA3095838@ax162> (raw)
In-Reply-To: <202502040638.5EF4863D8@keescook>

On Tue, Feb 04, 2025 at 06:40:25AM -0800, Kees Cook wrote:
> 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...

It seems like the error comes from bindgen. Does this patch help?

https://lore.kernel.org/all/20250129215003.1736127-1-jforbes@fedoraproject.org/

Cheers,
Nathan


      reply	other threads:[~2025-02-04 21:31 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
2025-02-04 20:10     ` Nathan Chancellor [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=20250204201019.GA3095838@ax162 \
    --to=nathan@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=catalin.marinas@arm.com \
    --cc=cki-project@redhat.com \
    --cc=kees@kernel.org \
    --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).