lkml.org 
[lkml]   [2020]   [Nov]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH 4.9 099/117] ftrace: Fix recursion check for NMI test
    Date
    From: Steven Rostedt (VMware) <rostedt@goodmis.org>

    commit ee11b93f95eabdf8198edd4668bf9102e7248270 upstream.

    The code that checks recursion will work to only do the recursion check once
    if there's nested checks. The top one will do the check, the other nested
    checks will see recursion was already checked and return zero for its "bit".
    On the return side, nothing will be done if the "bit" is zero.

    The problem is that zero is returned for the "good" bit when in NMI context.
    This will set the bit for NMIs making it look like *all* NMI tracing is
    recursing, and prevent tracing of anything in NMI context!

    The simple fix is to return "bit + 1" and subtract that bit on the end to
    get the real bit.

    Cc: stable@vger.kernel.org
    Fixes: edc15cafcbfa3 ("tracing: Avoid unnecessary multiple recursion checks")
    Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

    ---
    kernel/trace/trace.h | 3 ++-
    1 file changed, 2 insertions(+), 1 deletion(-)

    --- a/kernel/trace/trace.h
    +++ b/kernel/trace/trace.h
    @@ -542,7 +542,7 @@ static __always_inline int trace_test_an
    current->trace_recursion = val;
    barrier();

    - return bit;
    + return bit + 1;
    }

    static __always_inline void trace_clear_recursion(int bit)
    @@ -552,6 +552,7 @@ static __always_inline void trace_clear_
    if (!bit)
    return;

    + bit--;
    bit = 1 << bit;
    val &= ~bit;


    \
     
     \ /
      Last update: 2020-11-09 14:37    [W:4.025 / U:0.004 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site