[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20181005175356.cae90780f7c2fec361e406b7@kernel.org>
Date: Fri, 5 Oct 2018 17:53:56 +0900
From: Masami Hiramatsu <mhiramat@...nel.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
Dan Carpenter <dan.carpenter@...cle.com>
Subject: Re: [ftrace/kprobes PATCH 3/3] tracing/kprobes: Allow kprobe-events
to record module symbol
On Wed, 3 Oct 2018 21:11:28 -0400
Steven Rostedt <rostedt@...dmis.org> wrote:
> On Wed, 3 Oct 2018 15:12:27 -0400
> Steven Rostedt <rostedt@...dmis.org> wrote:
>
> > On Wed, 29 Aug 2018 01:18:43 +0900
> > Masami Hiramatsu <mhiramat@...nel.org> wrote:
> >
> > > Allow kprobe-events to record module symbols.
> > >
> > > Since data symbols in a non-loaded module doesn't exist, it fails to
> > > define such symbol as an argument of kprobe-event. But if the kprobe
> > > event is defined on that module, we can defer to resolve the symbol
> > > address.
> > >
> > > Note that if given symbol is not found, the event is kept unavailable.
> > > User can enable it but the event is not recorded.
> > >
> > >
> >
> > Hi Masami,
> >
> > The first two patches look like they should be applied now and marked
> > for stable, as they are fixes. This patch looks like an added feature,
> > and will go into the next merge window.
> >
> > Is that what you think too?
> >
>
> Heh, I just realized that this is on my kprobes branch. I was looking
> at it as if they were in mainline. Nevermind about the "stable"
> comment ;-)
Yes, ;) so I added [ftrace/kprobes] on the subject.
Anyway, these patches must be on top of that branch.
Thank you,
>
> -- Steve
--
Masami Hiramatsu <mhiramat@...nel.org>
Powered by blists - more mailing lists