From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: Bradley Morgan <bradley.morgan@linux.dev>, ritesh.list@gmail.com
Cc: brads@mainlining.org, chleroy@kernel.org,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
mpe@ellerman.id.au, npiggin@gmail.com, sshegde@linux.ibm.com
Subject: Re: [PATCH] powerpc32/modules: Reserve a PLT entry for ftrace_regs_caller
Date: Wed, 11 Nov 2026 17:28:28 +0530 [thread overview]
Message-ID: <371108c3-0314-4015-9ca4-d96a11f1e597@linux.ibm.com> (raw)
In-Reply-To: <80D9FEB3-9FB3-4878-BC66-74C13761CC9A@linux.dev>
On 11/11/26 12:58 PM, Bradley Morgan wrote:
> On 11 November 2026 03:48:41 GMT, Ritesh Harjani <ritesh.list@gmail.com>
> wrote:
>> Bradley Morgan <brads@mainlining.org> writes:
>>
>>> Commit 7dfbfb87c243 ("powerpc/ftrace: Activate
>>> HAVE_DYNAMIC_FTRACE_WITH_REGS on PPC32") made count_relocs()
>>> undercount the PLT entries the loader
>>> consumes: module_finalize_ftrace() now creates two trampolines
>>> (mod->arch.tramp for ftrace_caller() and mod->arch.tramp_regs for
>>> ftrace_regs_caller()), while count_relocs() reserves only one entry
>>> for ftrace.
>>>
>>> So the core .plt ends up one ppc_plt_entry (16 bytes) short. The
>>> walk in do_plt_call() scans for a free slot with
>>> "while (entry->jump[0])" and has no bound check, so once the last
>>> reserved slot is used up, the walk steps past the end of the section
>>> and patch_instruction() writes the 4-instruction trampoline into
>>> whatever module memory follows the .plt.
>>>
>>> Count the second entry, mirroring what module_64.c does for the same
>>> pair of stubs.
>>>
>>> Signed-off-by: Bradley Morgan <brads@mainlining.org>
>>> ---
>>> arch/powerpc/kernel/module_32.c | 3 +++
>>> 1 file changed, 3 insertions(+)
>>>
>> Do we also need fixes and stable tag here?
>>
>> Fixes: 7dfbfb87c243 ("powerpc/ftrace: Activate HAVE_DYNAMIC_FTRACE_WITH_REGS on PPC32")
>> Cc: stable@vger.kernel.org
> Hmm.. could the merger add that? If anyone merges.. :(
planned to be part of my fixes PR and will add it.
Thanks for the fix.
Maddy
>>
>> -ritesh
>>
> --- Thanks!
prev parent reply other threads:[~2026-11-11 11:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 17:56 Bradley Morgan
2026-11-10 8:57 ` Christophe Leroy (CS GROUP)
2026-11-10 21:22 ` Bradley Morgan
2026-11-11 3:48 ` Ritesh Harjani
2026-11-11 7:28 ` Bradley Morgan
2026-11-11 11:58 ` Madhavan Srinivasan [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=371108c3-0314-4015-9ca4-d96a11f1e597@linux.ibm.com \
--to=maddy@linux.ibm.com \
--cc=bradley.morgan@linux.dev \
--cc=brads@mainlining.org \
--cc=chleroy@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=ritesh.list@gmail.com \
--cc=sshegde@linux.ibm.com \
/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
all inboxes | Powered by JetHome®