Message-ID: <1480542127.27962.17.camel@tiscali.nl>
Subject: Re: Odd build breakage in 4.9-rc7
From: Paul Bolle <pebolle@tiscali.nl>
To: Jarod Wilson <jarod@redhat.com>
Cc: Tony Luck <tony.luck@intel.com>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Prarit Bhargava <prarit@redhat.com>, linux-kernel@vger.kernel.org
Date: Wed, 30 Nov 2016 22:42:07 +0100
In-Reply-To: <222b47f2-55e0-3410-c87d-183ca5e2a0fe@redhat.com>
References: <20161130172435.GG8563@redhat.com>
         <1480539150.27962.11.camel@tiscali.nl>
         <942ca543-de49-abda-7e3b-a8a31c0c2c88@redhat.com>
         <222b47f2-55e0-3410-c87d-183ca5e2a0fe@redhat.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 599
Lines: 18

On Wed, 2016-11-30 at 16:35 -0500, Jarod Wilson wrote:
> Just to confirm, with CONFIG_TRIM_UNUSED_KSYMS unset, the build behaves 
> normally, no ERROR spew.

And if MODVERSIONS is not set?

My current theory is that setting MODVERSIONS, somehow, hides the ERROR spew.
Because that could explain your bisect. Linus' commit turns of MODVERSIONS the
hard way. And, naturally, this theory fails if your .configs never had
MODVERSIONS set in the first place.

I'm testing all this right now, but you probably command more powerful
machines and could beat me in testing this theory.

Thanks,


Paul Bolle