public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Burke Libbey <burke.libbey@shopify.com>
Cc: linux-kernel@vger.kernel.org, mingo@kernel.org
Subject: Re: [PATCH] sched: reset sched_entity depth on changing parent
Date: Fri, 24 Oct 2014 17:58:05 +0200	[thread overview]
Message-ID: <20141024155805.GF21513@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20141024150746.GB25260@burke.local>

On Fri, Oct 24, 2014 at 11:07:46AM -0400, Burke Libbey wrote:
> From 2014-02-15: https://lkml.org/lkml/2014/2/15/217
> 
> This issue was reported and patched, but it still occurs in some situations on
> newer kernel versions.
> 
> [2249353.328452] BUG: unable to handle kernel NULL pointer dereference at 0000000000000150
> [2249353.336528] IP: [<ffffffff810b1cf7>] check_preempt_wakeup+0xe7/0x210
> 
> se.parent gets out of sync with se.depth, causing a panic when the algorithm in
> find_matching_se assumes they are correct. This patch forces se.depth to be
> updated every time se.parent is, so they can no longer become desync'd.
> 
> CC: Ingo Molnar <mingo@kernel.org>
> CC: Peter Zijlstra <peterz@infradead.org>
> Signed-off-by: Burke Libbey <burke.libbey@shopify.com>
> ---
> 
> I haven't been able to isolate the problem. Though I'm pretty confident this
> fixes the issue I've been having, I have not been able to prove it.

So this isn't correct, switching rq should not change depth. I suspect
you're just papering over the issue by frequently resetting the value,
which simply narrows the race window.


  reply	other threads:[~2014-10-24 15:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-24 15:07 [PATCH] sched: reset sched_entity depth on changing parent Burke Libbey
2014-10-24 15:58 ` Peter Zijlstra [this message]
2014-10-24 17:18   ` Kirill Tkhai
2014-10-27  9:49     ` Kirill Tkhai
2014-10-27 12:07     ` Peter Zijlstra
2014-10-27 12:40       ` Tejun Heo
2014-10-27 13:28         ` Peter Zijlstra
2014-10-27 13:36           ` Kirill Tkhai
2014-10-27 13:45             ` Peter Zijlstra
2014-10-27 13:48               ` Kirill Tkhai
2014-10-27 13:47           ` Tejun Heo
2014-10-27 13:48             ` Tejun Heo

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=20141024155805.GF21513@worktop.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=burke.libbey@shopify.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.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