diff options
| author | Tiezhu Yang <[email protected]> | 2023-04-19 12:07:27 +0800 |
|---|---|---|
| committer | Huacai Chen <[email protected]> | 2023-04-19 12:07:27 +0800 |
| commit | 370a3b8f58743eceb97c5256538d6048c26d2d03 (patch) | |
| tree | 64444dac60c812d9622e2d4e3f68150f313c7183 /lib/memory-notifier-error-inject.c | |
| parent | e32b3b8222204df8a2642a770f79ec2d7086faed (diff) | |
LoongArch: Check unwind_error() in arch_stack_walk()
We can see the following messages with CONFIG_PROVE_LOCKING=y on
LoongArch:
BUG: MAX_STACK_TRACE_ENTRIES too low!
turning off the locking correctness validator.
This is because stack_trace_save() returns a big value after call
arch_stack_walk(), here is the call trace:
save_trace()
stack_trace_save()
arch_stack_walk()
stack_trace_consume_entry()
arch_stack_walk() should return immediately if unwind_next_frame()
failed, no need to do the useless loops to increase the value of c->len
in stack_trace_consume_entry(), then we can fix the above problem.
Cc: [email protected]
Reported-by: Guenter Roeck <[email protected]>
Link: https://lore.kernel.org/all/[email protected]/
Signed-off-by: Tiezhu Yang <[email protected]>
Signed-off-by: Huacai Chen <[email protected]>
Diffstat (limited to 'lib/memory-notifier-error-inject.c')
0 files changed, 0 insertions, 0 deletions