linux-kernel - Re: [PATCH] riscv: stacktrace: fix backtracing through exceptions

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] [day] [month] [year] [list]

Message-Id: 
 <173643940723.1375203.17763630478007232527.git-patchwork-notify@kernel.org>
Date: Thu, 09 Jan 2025 16:16:47 +0000
From: patchwork-bot+linux-riscv@...nel.org
To: Clément Léger <cleger@...osinc.com>@codeaurora.org
Cc: linux-riscv@...ts.infradead.org, paul.walmsley@...ive.com,
 palmer@...belt.com, linux-kernel@...r.kernel.org, antonb@...storrent.com
Subject: Re: [PATCH] riscv: stacktrace: fix backtracing through exceptions

Hello:

This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@...osinc.com>:

On Mon,  9 Dec 2024 16:57:12 +0100 you wrote:
> Prior to commit 5d5fc33ce58e ("riscv: Improve exception and system call
> latency"), backtrace through exception worked since ra was filled with
> ret_from_exception symbol address and the stacktrace code checked 'pc' to
> be equal to that symbol. Now that handle_exception uses regular 'call'
> instructions, this isn't working anymore and backtrace stops at
> handle_exception(). Since there are multiple call site to C code in the
> exception handling path, rather than checking multiple potential return
> addresses, add a new symbol at the end of exception handling and check pc
> to be in that range.
> 
> [...]

Here is the summary with links:
  - riscv: stacktrace: fix backtracing through exceptions
    https://git.kernel.org/riscv/c/51356ce60e59

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html