From: Catalin Marinas Date: Tue, 13 Feb 2007 12:26:21 +0000 (+0100) Subject: [PATCH] x86-64: do not always end the stack trace with ULONG_MAX X-Git-Tag: v2.6.21-rc1~184^2~74 X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=006e84ee3a54e393ec6bef2a9bc891dc5bde2843;p=pandora-kernel.git [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 Signed-off-by: Andi Kleen Cc: Andi Kleen Cc: Jan Beulich Signed-off-by: Andrew Morton --- Reading git-diff-tree failed