projects / GitHub / LineageOS / android_kernel_motorola_exynos9610.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 5558870) | patch
[PATCH] x86-64: do not always end the stack trace with ULONG_MAX
authorCatalin Marinas <catalin.marinas@arm.com>
Tue, 13 Feb 2007 12:26:21 +0000 (13:26 +0100)
committerAndi Kleen <andi@basil.nowhere.org>
Tue, 13 Feb 2007 12:26:21 +0000 (13:26 +0100)
commit006e84ee3a54e393ec6bef2a9bc891dc5bde2843
tree1b30e4a1128ca880d7b91a7b994e0b268686bf06tree | snapshot (tar.gz zip)
parent5558870bfbcca10cfc7b13ab866687012ea3c9afcommit | diff
[PATCH] x86-64: do not always end the stack trace with ULONG_MAX

It makes more sense to end the stack trace with ULONG_MAX only if
nr_entries < max_entries.  Otherwise, we lose one entry in the long stack
traces and cannot know whether the trace was complete or not.

Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Signed-off-by: Andi Kleen <ak@suse.de>
Cc: Andi Kleen <ak@suse.de>
Cc: Jan Beulich <jbeulich@novell.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
arch/x86_64/kernel/stacktrace.c diff | blob | blame | history