From: Catalin Marinas <catalin.marinas@arm.com>
To: will@kernel.org, rostedt@goodmis.org, mhiramat@kernel.org,
mark.rutland@arm.com, samitolvanen@google.com, song@kernel.org,
ardb@kernel.org, dylanbhatch@google.com,
panfan <panfan@qti.qualcomm.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
kdong@qti.qualcomm.com, haijianc@qti.qualcomm.com
Subject: Re: [PATCH v2] arm64: ftrace: fix unreachable PLT for ftrace_caller in init_module with CONFIG_DYNAMIC_FTRACE
Date: Fri, 5 Sep 2025 17:13:50 +0100 [thread overview]
Message-ID: <175708881849.3546185.8607701618216308416.b4-ty@arm.com> (raw)
In-Reply-To: <20250905032236.3220885-1-panfan@qti.qualcomm.com>
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
prev parent reply other threads:[~2025-09-05 16:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 3:22 [PATCH v2] arm64: ftrace: fix unreachable PLT for ftrace_caller in init_module with CONFIG_DYNAMIC_FTRACE panfan
2025-09-05 9:07 ` Mark Rutland
2025-09-05 16:13 ` Catalin Marinas [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=175708881849.3546185.8607701618216308416.b4-ty@arm.com \
--to=catalin.marinas@arm.com \
--cc=ardb@kernel.org \
--cc=dylanbhatch@google.com \
--cc=haijianc@qti.qualcomm.com \
--cc=kdong@qti.qualcomm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=panfan@qti.qualcomm.com \
--cc=rostedt@goodmis.org \
--cc=samitolvanen@google.com \
--cc=song@kernel.org \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox