aboutsummaryrefslogtreecommitdiff
path: root/arch/loongarch/kernel/setup.c
diff options
context:
space:
mode:
authorGravatar Tiezhu Yang <yangtiezhu@loongson.cn> 2023-04-19 12:07:27 +0800
committerGravatar Huacai Chen <chenhuacai@loongson.cn> 2023-04-19 12:07:27 +0800
commit370a3b8f58743eceb97c5256538d6048c26d2d03 (patch)
tree64444dac60c812d9622e2d4e3f68150f313c7183 /arch/loongarch/kernel/setup.c
parentLoongArch: Adjust user_regset_copyin parameter to the correct offset (diff)
downloadlinux-370a3b8f58743eceb97c5256538d6048c26d2d03.tar.gz
linux-370a3b8f58743eceb97c5256538d6048c26d2d03.tar.bz2
linux-370a3b8f58743eceb97c5256538d6048c26d2d03.zip
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: stable@vger.kernel.org Reported-by: Guenter Roeck <linux@roeck-us.net> Link: https://lore.kernel.org/all/8a44ad71-68d2-4926-892f-72bfc7a67e2a@roeck-us.net/ Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn> Signed-off-by: Huacai Chen <chenhuacai@loongson.cn>
Diffstat (limited to 'arch/loongarch/kernel/setup.c')
0 files changed, 0 insertions, 0 deletions