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  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:   Fri, 12 May 2017 14:36:19 -0400
From:   Steven Rostedt <>
To:     "Paul E. McKenney" <>
Cc:, Thomas Gleixner <>,
        Peter Zijlstra <>,
        Ingo Molnar <>,
        Mathieu Desnoyers <>,
        Masami Hiramatsu <>
Subject: Re: [RFC][PATCH 1/5] tracing: Make sure RCU is watching before
 calling a stack trace

On Fri, 12 May 2017 11:25:35 -0700
"Paul E. McKenney" <> wrote:

> On Fri, May 12, 2017 at 01:15:45PM -0400, Steven Rostedt wrote:
> > From: "Steven Rostedt (VMware)" <>
> > 
> > As stack tracing now requires "rcu watching", force RCU to be watching when
> > recording a stack trace.
> > 
> > Signed-off-by: Steven Rostedt (VMware) <>  
> Assuming that you never get to __trace_stack() if in an NMI handler,
> this looks good to me!
> In contrast, if if __trace_stack() ever is called from an NMI handler,
> invoking rcu_irq_enter() can be fatal.

Then someone may die.

OK, what's the case of running this in nmi? How does perf do it?

Do we just skip the check if it is in an nmi?

	if (!in_nmi()) {
		if (unlikely(rcu_irq_enter_disabled()))


	if (!in_nmi())


-- Steve


Powered by blists - more mailing lists