mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Huang Ying <ying.huang@intel.com>, Ingo Molnar <mingo@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>, LKP ML <lkp@01.org>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [LKP] [sched] BUG: kernel boot hang
Date: Sun, 15 Feb 2015 13:18:07 -0500	[thread overview]
Message-ID: <20150215131807.30c1808c@grimm.local.home> (raw)
In-Reply-To: <20150215154620.GC8838@lerouge>

On Sun, 15 Feb 2015 16:46:22 +0100
Frederic Weisbecker <fweisbec@gmail.com> wrote:

> On Sun, Feb 15, 2015 at 03:43:28PM +0800, Huang Ying wrote:
> > FYI, we noticed the below changes on
> > 
> > commit a18b5d01819235629289212ad428a5ee2b40f0d9 ("sched: Fix missing preemption opportunity")

Looks to be something new (not in my tree).

/me checks out linux-next

> 
> Huang,
> 
> Can you please test the following patch and check if it still crashes?
> 
> Thanks.
> 
> 
> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> index c017a5f..a6d4d6c 100644
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -2879,7 +2879,7 @@ void __sched schedule_preempt_disabled(void)
>  	preempt_disable();
>  }
>  
> -static void preempt_schedule_common(void)
> +static void __sched notrace preempt_schedule_common(void)
>  {
>  	do {
>  		preempt_count_add(PREEMPT_ACTIVE);

Ah, since I added better recursion protection code in function tracer
this didn't break that. But unfortunately, function graph tracer
doesn't have that protection.

If it traces between preempt_schedule() and where it sets
PREEMPT_ACTIVE, it can indeed go into an infinite recursion. Yeah,
preempt_schedule_common() should be notrace, at least until we change
function_graph to have that recursion protection.

Acked-by: Steven Rostedt <rostedt@goodmis.org>

-- Steve


  reply	other threads:[~2015-02-15 18:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-15  7:43 Huang Ying
2015-02-15 15:31 ` Frederic Weisbecker
2015-02-15 15:38 ` Frederic Weisbecker
2015-02-15 15:46 ` Frederic Weisbecker
2015-02-15 18:18   ` Steven Rostedt [this message]
2015-02-16 15:07     ` Peter Zijlstra
2015-02-16 18:22       ` Frederic Weisbecker
2015-02-16 18:34         ` Steven Rostedt

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=20150215131807.30c1808c@grimm.local.home \
    --to=rostedt@goodmis.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=ying.huang@intel.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

all inboxes | Powered by JetHome®