From: "zhangwei(Jovi)" <jovi.zhangwei@huawei.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Oleg Nesterov <oleg@redhat.com>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@redhat.com>
Subject: [PATCH 0/2] tracing/kprobes&uprobes: some change on unregister logic
Date: Tue, 25 Jun 2013 16:15:39 +0800 [thread overview]
Message-ID: <51C951AB.5050201@huawei.com> (raw)
Hi,
This patchset change some logic on events unregistering of kprobes/uprobes
patch 1: kprobes event unregister cleanup
patch 2: fix a bug when calling unregister trace_uprobe
zhangwei(Jovi) (2):
tracing/kprobes: move free_trace_probe into unregister_trace_probe
tracing/uprobes: disallow unregister trace_uprobe when trace_uprobe
is in use
kernel/trace/trace_kprobe.c | 5 +----
kernel/trace/trace_uprobe.c | 51 ++++++++++++++++++++++++++++++++-----------
2 files changed, 39 insertions(+), 17 deletions(-)
--
1.7.9.7
reply other threads:[~2013-06-25 8:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=51C951AB.5050201@huawei.com \
--to=jovi.zhangwei@huawei.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=rostedt@goodmis.org \
--cc=srikar@linux.vnet.ibm.com \
/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