From: Li Zefan <lizf@cn.fujitsu.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@elte.hu>, Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Subject: Re: [PATCH] tracing/profile: Fix profile_disable vs module_unload
Date: Wed, 26 Aug 2009 15:44:07 +0800 [thread overview]
Message-ID: <4A94E7C7.70900@cn.fujitsu.com> (raw)
In-Reply-To: <1251272385.7538.1238.camel@twins>
>>>>>> Aahh, I see the bug, its only ftrace that knows about the module, not
>>>>>> tracepoints themselves, _that_ needs fixing.
>>>>> You could possibly do something like:
>>>>>
>>>>> struct module *tp_mod = __module_address(&some_tp_symbol);
>>>>> struct module *cb_mod = __module_text_address(func);
>>>>>
>>>>> if (tp_mod && tp_mod != cb_mod) {
>>>>> ret = try_get_module(tp_mod);
>>>>> if (ret)
>>>>> goto fail;
>>>>> }
>>>>>
>>>>> in register_trace_##name() or thereabout.
>>>>>
>>>> Actually I tried it, but it didn't work. As I said, You can't find
>>>> any tp symbol when registering tp callback. The same example again:
>>>>
>>>> In module bar, we have register_trace_foo()
>>>> In module foo, we have DEFINE_TRACE(foo) and trace_foo().
>>>>
>>>> bar doesn't know any symbol of foo, so it can't bump foo's refcnt,
>>> Well, clearly it knows about register_trace_foo() which itself knows at
>>> least one symbol that should be in module foo, right? How else could it
>>> register a callback in that module (if it were loaded)?
>>>
>>> It appears to use some intermediate code, in which case the intermediate
>>> code knows about foo, which too solves our problem.
>>>
>>>> *Note: you can load module bar without loading module foo*
>>> In which case the tracepoint registration fails, right?
>>>
>> No, it won't fail. ;)
>>
>> Instead, when foo is loaded, tracepoint_update_probe_range() will be
>> called, and the probe registered in bar will be added to the tracepoint.
>
> *blink*
>
> so we'll succeed in registering a tracepoint we know isn't there?
>
Yeah, try this:
# cd sample/tracepoints/
# insmod tracepoint-probe-sample.ko <--- load trace probe firstly
# insmod tracepoint-sample.ko <--- load tracepoint secondly
# cat /proc/tracepoint-sample
cat: /proc/tracepoint-sample: Operation not permitted <-- pls ignore this
# dmesg <-- see the output of probe
Event is encountered with filename tracepoint-sample
Event B is encountered
Event B is encountered
Event B is encountered
Event B is encountered
Event B is encountered
Event B is encountered
Event B is encountered
Event B is encountered
Event B is encountered
Event B is encountered
next prev parent reply other threads:[~2009-08-26 7:45 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 [this message]
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
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=4A94E7C7.70900@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--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