From: Peter Zijlstra <peterz@infradead.org>
To: kernel test robot <xiaolong.ye@intel.com>
Cc: Ingo Molnar <mingo@kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Andy Lutomirski <luto@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Borislav Petkov <bp@alien8.de>, Brian Gerst <brgerst@gmail.com>,
Denys Vlasenko <dvlasenk@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
lkp@01.org
Subject: Re: [lkp-robot] [debug] 19d436268d: BUG:unable_to_handle_kernel
Date: Thu, 6 Apr 2017 13:47:26 +0200 [thread overview]
Message-ID: <20170406114726.qnljok4vdfjgabno@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20170406025014.GM17682@yexl-desktop>
On Thu, Apr 06, 2017 at 10:50:14AM +0800, kernel test robot wrote:
>
> FYI, we noticed the following commit:
>
> commit: 19d436268dde95389c616bb3819da73f0a8b28a8 ("debug: Add _ONCE() logic to report_bug()")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
>
next/master doesn't build for me at all with your .config.
I get a metric ton of:
MODPOST 893 modules
LZ4 arch/x86/boot/compressed/vmlinux.bin.lz4
ERROR: "user_describe" [security/keys/trusted.ko] undefined!
ERROR: "__gcov_merge_add" [security/keys/trusted.ko] undefined!
ERROR: "__gcov_init" [security/keys/trusted.ko] undefined!
ERROR: "unregister_key_type" [security/keys/trusted.ko] undefined!
ERROR: "register_key_type" [security/keys/trusted.ko] undefined!
ERROR: "crypto_alloc_shash" [security/keys/trusted.ko] undefined!
ERROR: "tpm_seal_trusted" [security/keys/trusted.ko] undefined!
ERROR: "tpm_unseal_trusted" [security/keys/trusted.ko] undefined!
ERROR: "call_rcu" [security/keys/trusted.ko] undefined!
ERROR: "crypto_shash_digest" [security/keys/trusted.ko] undefined!
$ grep -c ERROR build.log
27293
prev parent reply other threads:[~2017-04-06 11:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 2:50 kernel test robot
2017-04-06 11:47 ` Peter Zijlstra [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=20170406114726.qnljok4vdfjgabno@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dvlasenk@redhat.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=xiaolong.ye@intel.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®