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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Fri, 10 Aug 2018 05:22:42 -0700
From:   Joel Fernandes <>
To:     Steven Rostedt <>
Cc:     LKML <>,
        Ingo Molnar <>,
        Andrew Morton <>,
        Joel Fernandes <>
Subject: Re: [for-next][PATCH 3/6] tracing: More reverting of "tracing:
 Centralize preemptirq tracepoints and unify their usage"

On Thu, Aug 9, 2018 at 2:03 PM, Steven Rostedt <> wrote:
> From: "Steven Rostedt (VMware)" <>
> Joel Fernandes created a nice patch that cleaned up the duplicate hooks used
> by lockdep and irqsoff latency tracer. It made both use tracepoints. But the
> latency tracer is triggering warnings when using tracepoints to call into
> the latency tracer's routines. Mainly, they can be called from NMI context.
> If that happens, then the SRCU may not work properly because on some
> architectures, SRCU is not safe to be called in both NMI and non-NMI
> context.
> This is a partial revert of the clean up patch c3bc8fd637a9 ("tracing:
> Centralize preemptirq tracepoints and unify their usage") that adds back the
> direct calls into the latency tracer. It also only calls the trace events
> when not in NMI.
> Cc: Joel Fernandes <>
> Fixes: c3bc8fd637a9 ("tracing: Centralize preemptirq tracepoints and unify their usage")
> Signed-off-by: Steven Rostedt (VMware) <>

Reviewed-by: Joel Fernandes (Google) <>


- Joel

Powered by blists - more mailing lists