x86/stacktrace: Remove the pointless ULONG_MAX marker
authorThomas Gleixner <tglx@linutronix.de>
Wed, 10 Apr 2019 10:27:56 +0000 (12:27 +0200)
committerThomas Gleixner <tglx@linutronix.de>
Sun, 14 Apr 2019 17:58:27 +0000 (19:58 +0200)
commitc5c27a0a583844c69a433039e4fd6396ba23551b
treecaee0c7cc12f7a26ad24b1b02bccb177da636a19
parentfdc7833964d83b7f7f39a03e2ee48a229ba0291f
x86/stacktrace: Remove the pointless ULONG_MAX marker

Terminating the last trace entry with ULONG_MAX is a completely pointless
exercise and none of the consumers can rely on it because it's
inconsistently implemented across architectures. In fact quite some of the
callers remove the entry and adjust stack_trace.nr_entries afterwards.

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Andy Lutomirski <luto@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Alexander Potapenko <glider@google.com>
Link: https://lkml.kernel.org/r/20190410103643.750954603@linutronix.de
arch/x86/kernel/stacktrace.c