The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Adam Williamson <awilliam@redhat.com>
To: Naveen N Rao <naveen@kernel.org>, Anthony Iliopoulos <ailiop@suse.com>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	 jforbes@redhat.com, kevin@scrye.com
Subject: Re: [PATCH] powerpc64/ftrace: fix module loading without patchable function entries
Date: Tue, 25 Mar 2025 18:16:53 -0700	[thread overview]
Message-ID: <89748fc85c6ca477f64e1a5cc1852e74c68b493c.camel@redhat.com> (raw)
In-Reply-To: <wlscshbqan2svtqkz5xc6v47tzndfnsvge7h4lbfn67zoplekl@elt2oxwhrp6f>

On Thu, 2025-02-13 at 22:29 +0530, Naveen N Rao wrote:
> On Wed, Feb 05, 2025 at 12:18:21AM +0100, Anthony Iliopoulos wrote:
> > get_stubs_size assumes that there must always be at least one patchable
> > function entry, which is not always the case (modules that export data
> > but no code), otherwise it returns -ENOEXEC and thus the section header
> > sh_size is set to that value. During module_memory_alloc() the size is
> > passed to execmem_alloc() after being page-aligned and thus set to zero
> > which will cause it to fail the allocation (and thus module loading) as
> > __vmalloc_node_range() checks for zero-sized allocs and returns null:
> > 
> > [  115.466896] module_64: cast_common: doesn't contain __patchable_function_entries.
> > [  115.469189] ------------[ cut here ]------------
> > [  115.469496] WARNING: CPU: 0 PID: 274 at mm/vmalloc.c:3778 __vmalloc_node_range_noprof+0x8b4/0x8f0
> > ...
> > [  115.478574] ---[ end trace 0000000000000000 ]---
> > [  115.479545] execmem: unable to allocate memory
> 
> Ugh, that's nasty.
> 
> > 
> > Fix this by removing the check completely, since it is anyway not
> > helpful to propagate this as an error upwards.
> > 
> > Fixes: eec37961a56a ("powerpc64/ftrace: Move ftrace sequence out of line")
> > Signed-off-by: Anthony Iliopoulos <ailiop@suse.com>
> > ---
> >  arch/powerpc/kernel/module_64.c | 4 ----
> >  1 file changed, 4 deletions(-)
> > 
> 
> Thanks for fixing this. It might also be good to add a check in 
> setup_ftrace_ool_stubs(). Something like this:
> 
> diff --git a/arch/powerpc/kernel/module_64.c b/arch/powerpc/kernel/module_64.c
> index 34a5aec4908f..c10a9c66cfe3 100644
> --- a/arch/powerpc/kernel/module_64.c
> +++ b/arch/powerpc/kernel/module_64.c
> @@ -1125,6 +1125,10 @@ static int setup_ftrace_ool_stubs(const Elf64_Shdr *sechdrs, unsigned long addr,
>         unsigned int i, total_stubs, num_stubs;
>         struct ppc64_stub_entry *stub;
>  
> +       /* Bail out early if no traceable functions */
> +       if (!me->arch.ool_stub_count)
> +               return 0;
> +
>         total_stubs = sechdrs[me->arch.stubs_section].sh_size / sizeof(*stub);
>         num_stubs = roundup(me->arch.ool_stub_count * sizeof(struct ftrace_ool_stub),
>                             sizeof(struct ppc64_stub_entry)) / sizeof(struct ppc64_stub_entry);
> 
> 
> Regardless of that, for this patch:
> Acked-by: Naveen N Rao (AMD) <naveen@kernel.org>
> 
> 
> - Naveen
> 
Is there anything that can be done to get this bumped along? It
completely breaks networking on Fedora's power9 boxes, as it affects
the i40e module which they use.

Thanks!
-- 
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org
https://www.happyassassin.net





  reply	other threads:[~2025-03-26  1:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-04 23:18 [PATCH] powerpc64/ftrace: fix module loading without patchable function entries Anthony Iliopoulos
2025-02-13 16:59 ` Naveen N Rao
2025-03-26  1:16   ` Adam Williamson [this message]
2025-03-26  1:44     ` Madhavan Srinivasan
2025-04-21  9:41 ` Madhavan Srinivasan

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=89748fc85c6ca477f64e1a5cc1852e74c68b493c.camel@redhat.com \
    --to=awilliam@redhat.com \
    --cc=ailiop@suse.com \
    --cc=jforbes@redhat.com \
    --cc=kevin@scrye.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=naveen@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