From: Jarod Wilson <jarod@redhat.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Tony Luck <tony.luck@intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Prarit Bhargava <prarit@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: Odd build breakage in 4.9-rc7
Date: Wed, 30 Nov 2016 16:35:34 -0500 [thread overview]
Message-ID: <222b47f2-55e0-3410-c87d-183ca5e2a0fe@redhat.com> (raw)
In-Reply-To: <942ca543-de49-abda-7e3b-a8a31c0c2c88@redhat.com>
On 2016-11-30 4:07 PM, Jarod Wilson wrote:
> On 2016-11-30 3:52 PM, Paul Bolle wrote:
>> On Wed, 2016-11-30 at 12:24 -0500, Jarod Wilson wrote:
>>> Up second, once we're past the above, building modules goes splat:
>>>
>>> ----8<----
>>> $ make -s ARCH=x86_64 V=1 -j8 modules
>>> ...
>>> ERROR: "module_put" [virt/lib/irqbypass.ko] undefined!
>>> ERROR: "mutex_unlock" [virt/lib/irqbypass.ko] undefined!
>>> ERROR: "mutex_lock" [virt/lib/irqbypass.ko] undefined!
>>> ...
>>> ----8<----
>>>
>>> There are similar ERROR lines to the tune of 145k lines of output,
>>> basically for every single module and symbol in the build. This breakage
>>> was bisected to commit cd3caefb4663e3811d37cc2afad3cce642d60061, which
>>> looks fairly innocuous, but when reverted, builds work fine again.
>>
>> I ran into a modules build printing over 100K ERROR lines a month ago:
>>
>> https://lkml.kernel.org/r/<1478165881-9263-1-git-send-email-pebolle@tiscali.nl>
>>
>>
>> That had to do with setting TRIM_UNUSED_KSYMS and so unsetting
>> UNUSED_SYMBOLS,
>> as far as I could tell. Did you perhaps also have UNUSED_SYMBOLS unset
>> when
>> your modules build when splat?
>
> I did indeed have CONFIG_TRIM_UNUSED_KSYMS=y and CONFIG_UNUSED_SYMBOLS
> unset.
Just to confirm, with CONFIG_TRIM_UNUSED_KSYMS unset, the build behaves
normally, no ERROR spew.
--
Jarod Wilson
jarod@redhat.com
next prev parent reply other threads:[~2016-11-30 21:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 17:24 Jarod Wilson
2016-11-30 18:18 ` Linus Torvalds
2016-11-30 18:28 ` Prarit Bhargava
2016-11-30 18:36 ` Linus Torvalds
2016-11-30 18:50 ` Prarit Bhargava
2016-11-30 19:00 ` Jarod Wilson
2016-11-30 19:35 ` Linus Torvalds
2016-11-30 22:41 ` Nicolas Pitre
2016-12-01 12:47 ` Prarit Bhargava
2016-12-01 14:03 ` Prarit Bhargava
2016-12-01 15:22 ` Jarod Wilson
2016-11-30 22:54 ` Nicolas Pitre
2016-11-30 20:52 ` Paul Bolle
2016-11-30 21:07 ` Jarod Wilson
2016-11-30 21:35 ` Jarod Wilson [this message]
2016-11-30 21:42 ` Paul Bolle
2016-11-30 21:57 ` Paul Bolle
2016-11-30 23:40 ` Jarod Wilson
2016-12-01 9:01 ` Paul Bolle
2016-12-01 13:46 ` Paul Bolle
2016-12-01 17:42 ` Nicolas Pitre
2016-12-01 20:15 ` Paul Bolle
2016-12-02 20:11 ` Nicolas Pitre
2016-12-02 22:41 ` Jarod Wilson
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=222b47f2-55e0-3410-c87d-183ca5e2a0fe@redhat.com \
--to=jarod@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=prarit@redhat.com \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®