mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Menglong Dong <menglong8.dong@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	oliver.sang@intel.com
Subject: Re: [PATCH] tracing: fprobe: Fix to init fprobe_ip_table earlier
Date: Thu, 2 Oct 2025 23:05:36 +0900	[thread overview]
Message-ID: <20251002230536.a0e15f3b016782c3bb9e5e9d@kernel.org> (raw)
In-Reply-To: <CADxym3Yvxs_Z6a1-EPziz79SBRsYHcaOH-CtvUhngYy3bJ71iA@mail.gmail.com>

On Thu, 2 Oct 2025 18:00:24 +0800
Menglong Dong <menglong8.dong@gmail.com> wrote:

> On Thu, Oct 2, 2025 at 4:39 PM Masami Hiramatsu (Google)
> <mhiramat@kernel.org> wrote:
> >
> > From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> >
> > Since the fprobe_ip_table is used from module unloading in
> > the failure path of load_module(), it must be initialized in
> > the earlier timing than late_initcall(). Unless that, the
> > fprobe_module_callback() will use an uninitialized spinlock of
> > fprobe_ip_table.
> >
> > Initialize fprobe_ip_table in core_initcall which is the same
> > timing as ftrace.
> >
> > Reported-by: kernel test robot <oliver.sang@intel.com>
> > Closes: https://lore.kernel.org/oe-lkp/202509301440.be4b3631-lkp@intel.com
> 
> Don't we need a Fixes tag here?

OK, I'll add it too.

> 
> The other part of this patch is LGTM.
> 
> Reviewed-by: Menglong Dong <menglong8.dong@gmail.com>

Thank you!


> 
> Thanks!
> Menglong Dong
> 
> > Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> > ---
> >  kernel/trace/fprobe.c |    2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/kernel/trace/fprobe.c b/kernel/trace/fprobe.c
> > index 95e43814b85b..99d83c08b9e2 100644
> > --- a/kernel/trace/fprobe.c
> > +++ b/kernel/trace/fprobe.c
> > @@ -847,4 +847,4 @@ static int __init fprobe_initcall(void)
> >         rhltable_init(&fprobe_ip_table, &fprobe_rht_params);
> >         return 0;
> >  }
> > -late_initcall(fprobe_initcall);
> > +core_initcall(fprobe_initcall);
> >


-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

      reply	other threads:[~2025-10-02 14:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-02  8:39 Masami Hiramatsu (Google)
2025-10-02 10:00 ` Menglong Dong
2025-10-02 14:05   ` Masami Hiramatsu [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=20251002230536.a0e15f3b016782c3bb9e5e9d@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=menglong8.dong@gmail.com \
    --cc=oliver.sang@intel.com \
    --cc=rostedt@goodmis.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

all inboxes | Powered by JetHome®