summaryrefslogtreecommitdiffstats
path: root/mm
diff options
context:
space:
mode:
authorPrakash Gupta <guptap@codeaurora.org>2017-09-14 01:28:32 +0200
committerLinus Torvalds <torvalds@linux-foundation.org>2017-09-14 03:53:16 +0200
commitbb53c820c5b0f1a52804e32683aa7874db27392d (patch)
tree83692dbb890f7a7f5b0fbda2c77d8f59a4095663 /mm
parentmm: treewide: remove GFP_TEMPORARY allocation flag (diff)
downloadlinux-bb53c820c5b0f1a52804e32683aa7874db27392d.tar.xz
linux-bb53c820c5b0f1a52804e32683aa7874db27392d.zip
arm64: stacktrace: avoid listing stacktrace functions in stacktrace
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. This was fixed for arch arm by commit 3683f44c42e9 ("ARM: stacktrace: avoid listing stacktrace functions in stacktrace") Link: http://lkml.kernel.org/r/1504078343-28754-1-git-send-email-guptap@codeaurora.org Signed-off-by: Prakash Gupta <guptap@codeaurora.org> Cc: Russell King <rmk+kernel@arm.linux.org.uk> Cc: Michal Hocko <mhocko@suse.com> Cc: Vlastimil Babka <vbabka@suse.cz> Cc: Will Deacon <will.deacon@arm.com> Cc: Catalin Marinas <catalin.marinas@arm.com> Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions