linux-kernel - Re: [PATCH v1] LoongArch: Handle special PC in unwind_next

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <226cffcb-2302-8afb-8be6-9cab2176d15b@loongson.cn>
Date: Thu, 27 Nov 2025 10:53:19 +0800
From: Jinyang He <hejinyang@...ngson.cn>
To: Bibo Mao <maobibo@...ngson.cn>, Tiezhu Yang <yangtiezhu@...ngson.cn>
Cc: Huacai Chen <chenhuacai@...nel.org>, Xi Zhang <zhangxi@...inos.cn>,
 Xianglai Li <lixianglai@...ngson.cn>, loongarch@...ts.linux.dev,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] LoongArch: Handle special PC in unwind_next_frame()

On 2025-11-27 09:53, Bibo Mao wrote:

>
> Just be curious, it is the same orc unwind method. why is clean with 
> file arch/x86/kernel/unwind_orc.c, however there is special handling 
> bt_address() in file arch/loongarch/kernel/unwind_orc.c ?
>
I'm not familiar with x86. Does it also copies exception handler to
other address like LoongArch? When backtrace to the copied exception
handler, its ORC info is not collected. The bt_address finds a
shadow PC to get the right ORC info and go on.

Thanks,
Jinyang