linux-kernel - Re: [PATCH 3/3][RFC] cpuidle/tracing: Denote the tracepoints as being in rcu_idle

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 07 Feb 2012 15:49:45 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	paulmck@...ux.vnet.ibm.com
Cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Rob Herring <robherring2@...il.com>,
	Nicolas Pitre <nicolas.pitre@...aro.org>,
	Kevin Hilman <khilman@...com>,
	Josh Triplett <josh@...htriplett.org>,
	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
	Len Brown <len.brown@...el.com>
Subject: Re: [PATCH 3/3][RFC] cpuidle/tracing: Denote the tracepoints as
 being in rcu_idle_exit() section

On Tue, 2012-02-07 at 07:40 -0800, Paul E. McKenney wrote:
> On Tue, Feb 07, 2012 at 09:56:56AM -0500, Steven Rostedt wrote:
> > From: Steven Rostedt <srostedt@...hat.com>
> > 
> > As the tracepoints in the cpuidle code are called when rcu_idle_exit() is in
> > effect, the _rcuidle() version must be used, otherwise the rcu_read_lock()s
> > that protect the tracepoint will not be honored.
> > 
> > Cc: Len Brown <len.brown@...el.com>
> > Cc: Paul E. McKenney <paulmck@...ux.vnet.ibm.com>
> > Signed-off-by: Steven Rostedt <rostedt@...dmis.org>
> 
> Looks good to me!
> 
> Reviewed-by: Paul E. McKenney <paulmck@...ux.vnet.ibm.com>

Thanks, but does this include patch 2/3 as well?

-- Steve


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/