archive mirror
 help / color / mirror / Atom feed
From: Andrew Jones <>
Subject: Re: linux-next: Tree for Apr 24
Date: Fri, 5 May 2017 20:55:50 +0200	[thread overview]
Message-ID: <20170505185550.xyhndktiw5gfbqix@hawk.localdomain> (raw)

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)
>                     ^
> ...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.


>From 0a8d642d17c6a93e927435ce9b6d2eaaeb19263b Mon Sep 17 00:00:00 2001
From: Andrew Jones <>
Date: Fri, 5 May 2017 19:54:35 +0200
Subject: [PATCH] jump_label: fix stack overflow

Fix a typo that leads to static_key_disable_cpuslocked infinitely
recursing.  This was found when the PMU kvm-unit-tests test for ARM
crashed the host and bisection lead to 924726b2b5e5 "perf: Cure
hotplug lock ordering issues".  That commit was just the victim,
the culprit commit is identified below in 'Fixes'.

Fixes: fc932a0477d0 "jump_label: Provide static_key_[disable|/slow_dec]_cpuslocked()"
Signed-off-by: Andrew Jones <>
 include/linux/jump_label.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/linux/jump_label.h b/include/linux/jump_label.h
index 6e3ebf2a39ede..bedd55849c2e3 100644
--- a/include/linux/jump_label.h
+++ b/include/linux/jump_label.h
@@ -259,7 +259,7 @@ static inline void static_key_disable(struct static_key *key)
 static inline void static_key_disable_cpuslocked(struct static_key *key)
-	static_key_disable_cpuslocked(key);
+	static_key_disable(key);
 #define STATIC_KEY_INIT_TRUE	{ .enabled = ATOMIC_INIT(1) }

             reply	other threads:[~2017-05-05 18:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-05 18:55 Andrew Jones [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-04-24 16:00 linux-next: Tree for Apr 24 broonie
2020-04-24  7:48 Stephen Rothwell
2019-04-24  9:12 Stephen Rothwell
2018-04-24  4:53 Stephen Rothwell
2017-04-24  8:10 Stephen Rothwell
2017-04-24 15:44 ` Paul Gortmaker
2015-04-24  4:50 Stephen Rothwell
2014-04-24  6:26 Stephen Rothwell
2013-04-24  8:07 Stephen Rothwell
2012-04-24  5:43 Stephen Rothwell

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170505185550.xyhndktiw5gfbqix@hawk.localdomain \ \ \ \ \ \ \ \

* 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).