diff options
| author | Thomas Gleixner <[email protected]> | 2019-04-10 12:27:59 +0200 |
|---|---|---|
| committer | Thomas Gleixner <[email protected]> | 2019-04-14 19:58:28 +0200 |
| commit | f8a9a269c28ddd5d741e747ceca753af01c828f2 (patch) | |
| tree | 6825f8abb8cc6cd8655c8338bf02df0e4f8afd50 | |
| parent | b01f6d368d296cac099383a3eb200e135420f885 (diff) | |
unicore32/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 <[email protected]>
Acked-by: Peter Zijlstra (Intel) <[email protected]>
Cc: Josh Poimboeuf <[email protected]>
Cc: Andy Lutomirski <[email protected]>
Cc: Steven Rostedt <[email protected]>
Cc: Alexander Potapenko <[email protected]>
Cc: Guan Xuetao <[email protected]>
Link: https://lkml.kernel.org/r/[email protected]
| -rw-r--r-- | arch/unicore32/kernel/stacktrace.c | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/arch/unicore32/kernel/stacktrace.c b/arch/unicore32/kernel/stacktrace.c index 9976e767d51c..e37da8c6837b 100644 --- a/arch/unicore32/kernel/stacktrace.c +++ b/arch/unicore32/kernel/stacktrace.c @@ -120,8 +120,6 @@ void save_stack_trace_tsk(struct task_struct *tsk, struct stack_trace *trace) } walk_stackframe(&frame, save_trace, &data); - if (trace->nr_entries < trace->max_entries) - trace->entries[trace->nr_entries++] = ULONG_MAX; } void save_stack_trace(struct stack_trace *trace) |