[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <175708881849.3546185.8607701618216308416.b4-ty@arm.com>
Date: Fri, 5 Sep 2025 17:13:50 +0100
From: Catalin Marinas <catalin.marinas@....com>
To: will@...nel.org,
rostedt@...dmis.org,
mhiramat@...nel.org,
mark.rutland@....com,
samitolvanen@...gle.com,
song@...nel.org,
ardb@...nel.org,
dylanbhatch@...gle.com,
panfan <panfan@....qualcomm.com>
Cc: linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org,
kdong@....qualcomm.com,
haijianc@....qualcomm.com
Subject: Re: [PATCH v2] arm64: ftrace: fix unreachable PLT for ftrace_caller in init_module with CONFIG_DYNAMIC_FTRACE
On Thu, 04 Sep 2025 20:22:36 -0700, panfan wrote:
> On arm64, it has been possible for a module's sections to be placed more
> than 128M away from each other since commit:
>
> commit 3e35d303ab7d ("arm64: module: rework module VA range selection")
>
> Due to this, an ftrace callsite in a module's .init.text section can be
> out of branch range for the module's ftrace PLT entry (in the module's
> .text section). Any attempt to enable tracing of that callsite will
> result in a BRK being patched into the callsite, resulting in a fatal
> exception when the callsite is later executed.
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64: ftrace: fix unreachable PLT for ftrace_caller in init_module with CONFIG_DYNAMIC_FTRACE
https://git.kernel.org/arm64/c/a7ed7b9d0ebb
--
Catalin
Powered by blists - more mailing lists