• Russell King's avatar
    ARM: stacktrace: avoid listing stacktrace functions in stacktrace · 3683f44c
    Russell King authored
    While debugging the FEC ethernet driver using stacktrace, it was noticed
    that the stacktraces always begin as follows:
    
     [<c00117b4>] save_stack_trace_tsk+0x0/0x98
     [<c0011870>] save_stack_trace+0x24/0x28
     ...
    
    This is because the stack trace code includes the stack frames for itself.
    This is incorrect behaviour, and also leads to "skip" doing the wrong
    thing (which is the number of stack frames to avoid recording.)
    
    Perversely, it does the right thing when passed a non-current thread.  Fix
    this by ensuring that we have a known constant number of frames above the
    main stack trace function, and always skip these.
    
    Cc: <stable@vger.kernel.org>
    Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
    3683f44c
stacktrace.c 3.53 KB