Re: linux-next: Tree for Apr 24

[Andrew Jones]

On Mon, Apr 24, 2017 at 11:44:13AM -0400, Paul Gortmaker wrote:
> There are also some new fails around kernel/events/core.c in arm32/arm64
> 
> include/linux/jump_label.h: In function
> âstatic_key_disable_cpuslocked.constprop.66â:
> include/linux/jump_label.h:260:20: error: inlining failed in call to
> always_inline âstatic_key_disable_cpuslocked.constprop.66â: recursive
> inlining
>  static inline void static_key_disable_cpuslocked(struct static_key *key)
>                     ^
> 
> http://kisskb.ellerman.id.au/kisskb/buildresult/13011884/
> http://kisskb.ellerman.id.au/kisskb/buildresult/13011947/
> ...and others.
> 
> A mindless automated bisect run came back with this:
> 
> 924726b2b5e5000dfb8eb6032651baed1b1bdc6c is the first bad commit
> commit 924726b2b5e5000dfb8eb6032651baed1b1bdc6c
> Author: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
> Date:   Sun Apr 23 12:13:09 2017 +0200
> 
>     perf: Cure hotplug lock ordering issues
> 
> I gave tglx and peterz a heads up on irc.
>

Sorry if this is a repeat, but I'm not sure if this has been resolved
yet, as I'm not on any of the mailing lists where it would be posted
and google isn't revealing anything besides this mail I'm replying to
(please keep me on CC in replies, as I'm not on the lists).

I bumped into a problem which bisecting led to this same commit.  And,
it turns out the problem is the same one pointed out above, i.e. the
recursive inlining report.  The following patch fixes the issue.

Thanks,
drew