linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: Li Zhong <zhong@linux.vnet.ibm.com>
Cc: linux-next list <linux-next@vger.kernel.org>,
	youquan.song@intel.com, rafael.j.wysocki@intel.com,
	paulmck@linux.vnet.ibm.com
Subject: Re: [PATCH linux-next] cpuidle: fix a suspicious RCU usage in menu governor
Date: Tue, 20 Nov 2012 11:04:09 -0500	[thread overview]
Message-ID: <50ABA9F9.1020105@redhat.com> (raw)
In-Reply-To: <1353404893.3694.42.camel@ThinkPad-T5421.cn.ibm.com>

On 11/20/2012 04:48 AM, Li Zhong wrote:
> I saw this suspicious RCU usage on the next tree of 11/15
>
> [   67.123404] ===============================
> [   67.123413] [ INFO: suspicious RCU usage. ]
> [   67.123423] 3.7.0-rc5-next-20121115-dirty #1 Not tainted
> [   67.123434] -------------------------------
> [   67.123444] include/trace/events/timer.h:186 suspicious rcu_dereference_check() usage!

> hrtimer_start was added in 198fd638 and ae515197. The patch below tries
> to use RCU_NONIDLE around it to avoid the above report.
>
> Signed-off-by: Li Zhong <zhong@linux.vnet.ibm.com>

Reviewed-by: Rik van Riel <riel@redhat.com>

-- 
All rights reversed

  parent reply	other threads:[~2012-11-20 16:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-20  9:48 [PATCH linux-next] cpuidle: fix a suspicious RCU usage in menu governor Li Zhong
2012-11-20 15:34 ` Paul E. McKenney
2012-11-20 16:04 ` Rik van Riel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-11-22  1:45 Li Zhong
2012-11-22 23:12 ` Rafael J. Wysocki

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=50ABA9F9.1020105@redhat.com \
    --to=riel@redhat.com \
    --cc=linux-next@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=youquan.song@intel.com \
    --cc=zhong@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).