um/stacktrace: Remove the pointless ULONG_MAX marker
authorThomas Gleixner <tglx@linutronix.de>
Wed, 10 Apr 2019 10:27:55 +0000 (12:27 +0200)
committerThomas Gleixner <tglx@linutronix.de>
Sun, 14 Apr 2019 17:58:27 +0000 (19:58 +0200)
commitfdc7833964d83b7f7f39a03e2ee48a229ba0291f
treed7e767d708df8139f907a11b3b85f3a35d391c2a
parent4443f8e6ac7755cd775c70d08be8042dc2f936cb
um/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>
Cc: Richard Weinberger <richard@nod.at>
Cc: linux-um@lists.infradead.org
Link: https://lkml.kernel.org/r/20190410103643.662853876@linutronix.de
arch/um/kernel/stacktrace.c