linux-kernel - Re: [RFC][PATCH 15/18 v2] ftrace/rcu: Mark functions that are RCU unsafe

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:	Sat, 31 Aug 2013 16:43:24 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	paulmck@...ux.vnet.ibm.com
Cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Jiri Olsa <jolsa@...hat.com>
Subject: Re: [RFC][PATCH 15/18 v2] ftrace/rcu: Mark functions that are RCU
 unsafe

On Sat, 2013-08-31 at 13:00 -0700, Paul E. McKenney wrote:
> On Sat, Aug 31, 2013 at 01:11:32AM -0400, Steven Rostedt wrote:
> > From: "Steven Rostedt (Red Hat)" <rostedt@...dmis.org>
> > 
> > Some callbacks of the function tracer use rcu_read_lock(). This means that
> > there's places that can not be traced because RCU is not tracking the CPU
> > for various reasons (like NO_HZ_FULL and coming back from userspace).
> > 
> > Thes functions need to be marked so that callbacks that use RCU do not
> > trace them.
> > 
> > Cc: Paul E. McKenney <paulmck@...ux.vnet.ibm.com>
> > Signed-off-by: Steven Rostedt <rostedt@...dmis.org>
> 
> Reviewed-by: Paul E. McKenney <paulmck@...ux.vnet.ibm.com>
> 
> Please let me know if you would like me to take this one.  If I don't
> hear otherwise, I will assume that you are pushing it.
> 

These I rather take, as they are all dependent on the previous changes.

Thanks!

-- 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/