From: Peter Zijlstra <peterz@infradead.org>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ben Segall <bsegall@google.com>, LKP <lkp@01.org>,
linux-kernel@vger.kernel.org
Subject: Re: [sched] WARNING: CPU: 0 PID: 0 at kernel/time/hrtimer.c:802 hrtimer_forward()
Date: Fri, 1 May 2015 12:10:07 +0200 [thread overview]
Message-ID: <20150501101007.GB5029@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20150501044713.GA4365@wfg-t540p.sh.intel.com>
On Fri, May 01, 2015 at 12:47:13PM +0800, Fengguang Wu wrote:
> commit 77a4d1a1b9a122ca1fa3507bd30aec1520d7a8a4
> sched: Cleanup bandwidth timers
> [ 64.000438] WARNING: CPU: 0 PID: 0 at kernel/time/hrtimer.c:802 hrtimer_forward+0x71/0x189()
Argh, yes of course. The problem is that the timer can be re-started
before the handler acquires the lock, and therefore the hrtimer_forwards
in the handler will trigger that WARN.
Lemme try and go convince this heap of snot that's occupying my brain
cavity to produce coherent thought and come up with a nice fix for that.
parent reply other threads:[~2015-05-01 10:10 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20150501044713.GA4365@wfg-t540p.sh.intel.com>]
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=20150501101007.GB5029@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bsegall@google.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=tglx@linutronix.de \
/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®