linux-kernel - Re: [PATCH v2 0/2] ftrace: Make ftrace

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: 
 <173395639774.1729195.5975449690225774291.git-patchwork-notify@kernel.org>
Date: Wed, 11 Dec 2024 22:33:17 +0000
From: patchwork-bot+linux-riscv@...nel.org
To: Steven Rostedt <rostedt@...dmis.org>
Cc: linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
 linux-trace-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
 loongarch@...ts.linux.dev, linuxppc-dev@...ts.ozlabs.org,
 linux-s390@...r.kernel.org, linux-arch@...r.kernel.org, x86@...nel.org,
 mhiramat@...nel.org, mathieu.desnoyers@...icios.com, mark.rutland@....com,
 catalin.marinas@....com, will@...nel.org, chenhuacai@...nel.org,
 kernel@...0n.name, mpe@...erman.id.au, npiggin@...il.com,
 christophe.leroy@...roup.eu, naveen@...nel.org, maddy@...ux.ibm.com,
 paul.walmsley@...ive.com, palmer@...belt.com, aou@...s.berkeley.edu,
 hca@...ux.ibm.com, gor@...ux.ibm.com, agordeev@...ux.ibm.com,
 borntraeger@...ux.ibm.com, svens@...ux.ibm.com, tglx@...utronix.de,
 mingo@...nel.org, bp@...en8.de, dave.hansen@...ux.intel.com
Subject: Re: [PATCH v2 0/2] ftrace: Make ftrace_regs abstract and consolidate code

Hello:

This series was applied to riscv/linux.git (fixes)
by Steven Rostedt (Google) <rostedt@...dmis.org>:

On Tue, 08 Oct 2024 19:05:27 -0400 you wrote:
> This is based on:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git/
>      ftrace/for-next
> 
> ftrace_regs was created to hold registers that store information to save
> function parameters, return value and stack. Since it is a subset of
> pt_regs, it should only be used by its accessor functions. But because
> pt_regs can easily be taken from ftrace_regs (on most archs), it is
> tempting to use it directly. But when running on other architectures, it
> may fail to build or worse, build but crash the kernel!
> 
> [...]

Here is the summary with links:
  - [v2,1/2] ftrace: Make ftrace_regs abstract from direct use
    https://git.kernel.org/riscv/c/7888af4166d4
  - [v2,2/2] ftrace: Consolidate ftrace_regs accessor functions for archs using pt_regs
    (no matching commit)

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