From: kbuild test robot <lkp@intel.com>
To: Vegard Nossum <vegard.nossum@oracle.com>
Cc: kbuild-all@01.org, Akinobu Mita <akinobu.mita@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org,
Vegard Nossum <vegard.nossum@oracle.com>
Subject: Re: [PATCH 09/10] fault injection: spin_trylock() fault injection
Date: Thu, 4 Aug 2016 06:02:05 +0800 [thread overview]
Message-ID: <201608040532.wozpJnsW%fengguang.wu@intel.com> (raw)
In-Reply-To: <1470236755-29844-9-git-send-email-vegard.nossum@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 2723 bytes --]
Hi Vegard,
[auto build test ERROR on linus/master]
[also build test ERROR on next-20160803]
[cannot apply to v4.7]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Vegard-Nossum/fault-injection-fix-a-few-documentation-errors/20160803-233940
config: x86_64-allmodconfig (attached as .config)
compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
Note: the linux-review/Vegard-Nossum/fault-injection-fix-a-few-documentation-errors/20160803-233940 HEAD 4d292f00c3ab33b58cdd8a3781d1e0126f9e7fb8 builds fine.
It only hurts bisectibility.
All errors (new ones prefixed by >>):
ERROR: "should_fail_spinlock" [sound/core/snd-pcm.ko] undefined!
ERROR: "should_fail_spinlock" [net/sched/sch_teql.ko] undefined!
ERROR: "should_fail_spinlock" [net/ipv6/ipv6.ko] undefined!
ERROR: "should_fail_spinlock" [fs/xfs/xfs.ko] undefined!
ERROR: "should_fail_spinlock" [fs/gfs2/gfs2.ko] undefined!
ERROR: "should_fail_spinlock" [fs/fscache/fscache.ko] undefined!
ERROR: "should_fail_spinlock" [fs/ext4/ext4.ko] undefined!
ERROR: "should_fail_spinlock" [fs/ext2/ext2.ko] undefined!
ERROR: "should_fail_spinlock" [fs/autofs4/autofs4.ko] undefined!
ERROR: "should_fail_spinlock" [drivers/net/ifb.ko] undefined!
ERROR: "should_fail_spinlock" [drivers/net/ethernet/qlogic/qlcnic/qlcnic.ko] undefined!
ERROR: "should_fail_spinlock" [drivers/net/ethernet/qlogic/netxen/netxen_nic.ko] undefined!
ERROR: "should_fail_spinlock" [drivers/net/ethernet/nvidia/forcedeth.ko] undefined!
ERROR: "should_fail_spinlock" [drivers/net/ethernet/neterion/vxge/vxge.ko] undefined!
ERROR: "should_fail_spinlock" [drivers/net/ethernet/myricom/myri10ge/myri10ge.ko] undefined!
ERROR: "should_fail_spinlock" [drivers/net/ethernet/chelsio/cxgb4vf/cxgb4vf.ko] undefined!
ERROR: "should_fail_spinlock" [drivers/net/ethernet/chelsio/cxgb4/cxgb4.ko] undefined!
ERROR: "should_fail_spinlock" [drivers/net/ethernet/chelsio/cxgb3/cxgb3.ko] undefined!
ERROR: "should_fail_spinlock" [drivers/net/ethernet/chelsio/cxgb/cxgb.ko] undefined!
>> ERROR: "should_fail_spinlock" [drivers/net/ethernet/cavium/liquidio/liquidio.ko] undefined!
ERROR: "should_fail_spinlock" [drivers/net/ethernet/3com/typhoon.ko] undefined!
ERROR: "should_fail_spinlock" [drivers/char/ipmi/ipmi_msghandler.ko] undefined!
ERROR: "should_fail_spinlock" [drivers/atm/lanai.ko] undefined!
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 55553 bytes --]
next prev parent reply other threads:[~2016-08-03 22:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 15:05 [PATCH 01/10] fault injection: fix a few documentation errors Vegard Nossum
2016-08-03 15:05 ` [PATCH 02/10] fault injection: fix Kconfig menu Vegard Nossum
2016-08-03 15:05 ` [PATCH 03/10] fault injection: allow FAULT_INJECTION_STACKTRACE_FILTER on X86_64 Vegard Nossum
2016-08-03 15:05 ` [PATCH 04/10] fault injection: prevent recursive fault injection Vegard Nossum
2016-08-03 15:05 ` [PATCH 05/10] fault injection: mutex_trylock() " Vegard Nossum
2016-08-03 16:07 ` kbuild test robot
2016-08-03 18:15 ` kbuild test robot
2016-08-03 15:05 ` [PATCH 06/10] fault injection: rt_mutex_trylock() " Vegard Nossum
2016-08-03 15:05 ` [PATCH 07/10] fault injection: down_trylock() " Vegard Nossum
2016-08-03 15:05 ` [PATCH 08/10] fault injection: down_{read,write}_trylock() " Vegard Nossum
2016-08-03 15:05 ` [PATCH 09/10] fault injection: spin_trylock() " Vegard Nossum
2016-08-03 22:02 ` kbuild test robot [this message]
2016-08-03 22:11 ` kbuild test robot
2016-08-03 15:05 ` [PATCH 10/10] fault injection: inject faults in new/rare callchains Vegard Nossum
2016-08-08 13:54 ` Akinobu Mita
2016-08-08 14:07 ` Vegard Nossum
2016-08-08 16:24 ` Akinobu Mita
2016-10-16 15:56 [PATCH 01/10] fault injection: fix a few documentation errors Vegard Nossum
2016-10-16 15:56 ` [PATCH 09/10] fault injection: spin_trylock() fault injection Vegard Nossum
2016-10-16 16:28 ` Peter Zijlstra
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=201608040532.wozpJnsW%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akinobu.mita@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=vegard.nossum@oracle.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;
as well as URLs for NNTP newsgroup(s).