From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: linux-kernel@vger.kernel.org,
Josh Triplett <josh@joshtriplett.org>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <laijs@cn.fujitsu.com>
Subject: Re: [PATCH] rcu: don't use __this_cpu_* from preemptible context
Date: Tue, 30 Dec 2014 17:59:16 -0800 [thread overview]
Message-ID: <20141231015916.GM11609@linux.vnet.ibm.com> (raw)
In-Reply-To: <1419785381-26133-1-git-send-email-sasha.levin@oracle.com>
On Sun, Dec 28, 2014 at 11:49:40AM -0500, Sasha Levin wrote:
> Commit "rcu: Make cond_resched_rcu_qs() apply to normal RCU flavors" has added
> debug code which tries to read from __this_cpu in a preemptible code, which
> doesn't work too well.
>
> Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
Good catch, queued for 3.20 (same as the offending commit).
Thanx, Paul
> ---
> kernel/rcu/tree_trace.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/rcu/tree_trace.c b/kernel/rcu/tree_trace.c
> index a9b79ca..fbb6240 100644
> --- a/kernel/rcu/tree_trace.c
> +++ b/kernel/rcu/tree_trace.c
> @@ -122,7 +122,7 @@ static void print_one_rcu_data(struct seq_file *m, struct rcu_data *rdp)
> cpu_is_offline(rdp->cpu) ? '!' : ' ',
> ulong2long(rdp->completed), ulong2long(rdp->gpnum),
> rdp->passed_quiesce,
> - rdp->rcu_qs_ctr_snap == __this_cpu_read(rcu_qs_ctr),
> + rdp->rcu_qs_ctr_snap == per_cpu(rcu_qs_ctr, rdp->cpu),
> rdp->qs_pending);
> seq_printf(m, " dt=%d/%llx/%d df=%lu",
> atomic_read(&rdp->dynticks->dynticks),
> --
> 1.7.10.4
>
prev parent reply other threads:[~2014-12-31 12:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-28 16:49 [PATCH] rcu: don't use __this_cpu_* from preemptible context Sasha Levin
2014-12-31 1:59 ` Paul E. McKenney [this message]
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=20141231015916.GM11609@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.org \
--cc=sasha.levin@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.