From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Li Zefan <lizf@cn.fujitsu.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@elte.hu>,
Frederic Weisbecker <fweisbec@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tracing/profile: Fix profile_disable vs module_unload
Date: Wed, 26 Aug 2009 15:53:45 -0400 [thread overview]
Message-ID: <20090826195345.GB5298@Krystal> (raw)
In-Reply-To: <alpine.DEB.2.00.0908261544590.11291@gandalf.stny.rr.com>
* Steven Rostedt (rostedt@goodmis.org) wrote:
>
>
>
> On Wed, 26 Aug 2009, Mathieu Desnoyers wrote:
>
> > * Mathieu Desnoyers (mathieu.desnoyers@polymtl.ca) wrote:
> > > * Steven Rostedt (rostedt@goodmis.org) wrote:
> > > >
> > > > This patch solves the problem that Li originally reported. If something
> > > > registers a trace point belonging to a module, then it ups the ref count
> > > > of the module. This prevents a process from registering a probe to a
> > > > tracepoint belonging to a module and then having the module disappear.
> > > >
> > > > Doing the example with perf in Li's original post, now errors on the
> > > > rmmod, with "ERROR: Module trace_events_sample is in use".
> > > >
> > > > Mathieu, can I have your acked-by on this?
> > > >
> > >
> > > Sorry, it looks buggy.
>
> Well, it is not that buggy. It would only prevent modules from unloading
> if another tracepoint with the same name and parameters had a probe
> registered. More of a too big of a tent deal.
>
> > >
> > > It does not deal with the fact that tracepoints with the same name and
> > > arguments can be present in more than one module, or in a combination of
> > > kernel core and modules.
> > >
> > > The struct tracepoint_entry is specific to a a tracepoint name, used for
> > > registration, but is eventually tied to all tracepoint instrumentation
> > > instances for this tracepoint name.
> > >
>
> Anyway, this prevents your tracepoints from doing the odd things of
> loading a probe before it exists. Well you can, but then you prevent the
> unload of the module that registered it. Fine, I chucked out that patch.
>
you should try adding the required tracepoint_synchronize_unregister()
call to ftrace_profile_disable_##call in ftrace.h. I expect this will
fix your problem.
Note that this is a bit slow to call it at each unregistration. Ideally,
a module containing tracepoint probes should call this synchronization
primitive only once at module unload.
Mathieu
> >
> > Looking at the original post:
> > http://lkml.org/lkml/2009/8/24/5
> >
> > the problem seems to be caused by the fact that the
> > trace_event_profile.c keeps some knowledge of modules in internal data
> > structures, but does not get notified of module unloads. Why don't we
> > fix that instead ?
> >
> > A quick glance at it seems to indicate that it lazily discovers new
> > modules when the tracepoints are hit. Using module load/unload notifiers
> > would be more appropriate. Or maybe adding a notifier call to
> > tracepoint.c, calling notification callbacks for probe modules which
> > need to know when the connected tracepoints are changing
> > (when they are connected/disconnected) would probably be even more
> > appropriate. As a result, it would remove the dynamic verification cost
> > implied by lazy data structure lookup and check each time the probe is
> > fired.
>
> Peter is correct that he should not need to worry about modules, he
> doesn't build kernels with them ;-)
>
> Here's another patch that moves the module ref count administration to the
> trace events themselves. This should satisfy both you and Peter.
>
> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
>
> diff --git a/include/trace/ftrace.h b/include/trace/ftrace.h
> index 1b1f742..3f7c5dc 100644
> --- a/include/trace/ftrace.h
> +++ b/include/trace/ftrace.h
> @@ -390,6 +390,20 @@ static inline int ftrace_get_offsets_##call( \
> *
> */
>
> +#ifdef MODULE
> +# define event_trace_up_ref() \
> + do { \
> + if (!try_module_get(THIS_MODULE)) { \
> + atomic_dec(&event_call->profile_count); \
> + return -1; \
> + } \
> + } while (0)
> +# define event_trace_down_ref() module_put(THIS_MODULE)
> +#else
> +# define event_trace_up_ref() do { } while (0)
> +# define event_trace_down_ref() do { } while (0)
> +#endif
> +
> #undef TRACE_EVENT
> #define TRACE_EVENT(call, proto, args, tstruct, assign, print) \
> \
> @@ -399,16 +413,20 @@ static int ftrace_profile_enable_##call(struct ftrace_event_call *event_call) \
> { \
> int ret = 0; \
> \
> - if (!atomic_inc_return(&event_call->profile_count)) \
> + if (!atomic_inc_return(&event_call->profile_count)) { \
> + event_trace_up_ref(); \
> ret = register_trace_##call(ftrace_profile_##call); \
> + } \
> \
> return ret; \
> } \
> \
> static void ftrace_profile_disable_##call(struct ftrace_event_call *event_call)\
> { \
> - if (atomic_add_negative(-1, &event_call->profile_count)) \
> + if (atomic_add_negative(-1, &event_call->profile_count)) { \
> unregister_trace_##call(ftrace_profile_##call); \
> + event_trace_down_ref(); \
> + } \
> }
>
> #include TRACE_INCLUDE(TRACE_INCLUDE_FILE)
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next prev parent reply other threads:[~2009-08-26 19:53 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 4:19 [PATCH] tracing/profile: Fix profile_disable vs module_unload Li Zefan
2009-08-24 6:01 ` Peter Zijlstra
2009-08-24 6:22 ` Li Zefan
2009-08-24 6:56 ` Peter Zijlstra
2009-08-24 9:24 ` Ingo Molnar
2009-08-24 9:27 ` Peter Zijlstra
2009-08-24 16:13 ` Steven Rostedt
2009-08-25 5:22 ` Li Zefan
2009-08-25 6:21 ` Peter Zijlstra
2009-08-25 6:33 ` Li Zefan
2009-08-25 6:40 ` Peter Zijlstra
2009-08-25 9:05 ` Ingo Molnar
2009-08-25 9:12 ` Peter Zijlstra
2009-08-25 10:22 ` Ingo Molnar
2009-08-25 10:32 ` Peter Zijlstra
2009-08-25 10:39 ` Ingo Molnar
2009-08-25 10:47 ` Peter Zijlstra
2009-08-25 14:52 ` Peter Zijlstra
2009-08-26 6:18 ` Li Zefan
2009-08-26 6:46 ` Peter Zijlstra
2009-08-26 6:52 ` Peter Zijlstra
2009-08-26 7:01 ` Peter Zijlstra
2009-08-26 7:10 ` Li Zefan
2009-08-26 7:26 ` Peter Zijlstra
2009-08-26 7:31 ` Li Zefan
2009-08-26 7:39 ` Peter Zijlstra
2009-08-26 7:44 ` Li Zefan
2009-08-26 14:37 ` Steven Rostedt
2009-08-26 16:46 ` Mathieu Desnoyers
2009-08-26 17:48 ` Steven Rostedt
2009-08-26 18:01 ` Mathieu Desnoyers
2009-08-26 18:17 ` Mathieu Desnoyers
2009-08-26 19:48 ` Steven Rostedt
2009-08-26 19:53 ` Mathieu Desnoyers [this message]
2009-08-26 21:21 ` Steven Rostedt
2009-08-26 22:29 ` Mathieu Desnoyers
2009-08-27 1:53 ` Li Zefan
2009-08-27 2:13 ` Steven Rostedt
2009-08-27 14:39 ` Mathieu Desnoyers
2009-08-27 14:56 ` Steven Rostedt
2009-08-27 15:11 ` Mathieu Desnoyers
2009-08-27 15:51 ` Steven Rostedt
2009-08-27 15:59 ` Mathieu Desnoyers
2009-08-27 16:03 ` Steven Rostedt
2009-08-27 6:25 ` Peter Zijlstra
2009-08-27 15:57 ` Steven Rostedt
2009-08-27 16:04 ` Peter Zijlstra
2009-08-27 16:18 ` Steven Rostedt
2009-08-27 1:01 ` Li Zefan
2009-08-26 19:14 ` Peter Zijlstra
2009-08-26 19:44 ` Mathieu Desnoyers
2009-09-13 15:02 ` [tip:tracing/core] tracing/profile: fix " tip-bot for Li Zefan
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=20090826195345.GB5298@Krystal \
--to=mathieu.desnoyers@polymtl.ca \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--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