Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754681AbZIKQIR (ORCPT ); Fri, 11 Sep 2009 12:08:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754653AbZIKQIP (ORCPT ); Fri, 11 Sep 2009 12:08:15 -0400 Received: from mx1.redhat.com ([209.132.183.28]:57177 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754652AbZIKQIO (ORCPT ); Fri, 11 Sep 2009 12:08:14 -0400 Message-ID: <4AAA76B1.3020208@redhat.com> Date: Fri, 11 Sep 2009 12:11:29 -0400 From: Masami Hiramatsu User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.1) Gecko/20090814 Fedora/3.0-2.6.b3.fc11 Thunderbird/3.0b3 MIME-Version: 1.0 To: rostedt@goodmis.org CC: Frederic Weisbecker , Ingo Molnar , lkml , systemtap , DLE , Jim Keniston , Ananth N Mavinakayanahalli , Andi Kleen , Christoph Hellwig , "Frank Ch. Eigler" , "H. Peter Anvin" , Jason Baron , "K.Prasad" , Lai Jiangshan , Li Zefan , Peter Zijlstra , Srikar Dronamraju , Tom Zanussi Subject: Re: [PATCH tracing/kprobes 5/7] tracing/kprobes: Add argument name support References: <20090910235258.22412.29317.stgit@dhcp-100-2-132.bos.redhat.com> <20090910235337.22412.77383.stgit@dhcp-100-2-132.bos.redhat.com> <1252678079.18996.665.camel@gandalf.stny.rr.com> In-Reply-To: <1252678079.18996.665.camel@gandalf.stny.rr.com> Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1647 Lines: 53 Steven Rostedt wrote: > On Thu, 2009-09-10 at 19:53 -0400, Masami Hiramatsu wrote: > >> @@ -870,9 +892,13 @@ print_kprobe_event(struct trace_iterator *iter, int flags) >> { >> struct kprobe_trace_entry *field; >> struct trace_seq *s =&iter->seq; >> + struct trace_event *event; >> + struct trace_probe *tp; >> int i; >> >> field = (struct kprobe_trace_entry *)iter->ent; >> + event = ftrace_find_event(field->ent.type); >> + tp = container_of(event, struct trace_probe, event); > > Can this function be called the data is in the ring buffer, but the > probe has been unregistered? If so, the result of ftrace_find_event be > NULL? Hmm, it will depend on ftrace implementation. Before releasing trace_probe, kprobe tracer tries to unregister event call. If it's correctly locking mutex or some rw_lock for both of unregistering and printing, it will be safe. Unfortunately, it seems not :-(. In trace_events.c, 1054 static void __trace_remove_event_call(struct ftrace_event_call *call) 1055 { 1056 ftrace_event_enable_disable(call, 0); 1057 if (call->event) 1058 __unregister_ftrace_event(call->event); What we need to do is calling unregister_ftrace_event() instead of __unregister_ftrace_event. Thank you, -- Masami Hiramatsu Software Engineer Hitachi Computer Products (America), Inc. Software Solutions Division e-mail: mhiramat@redhat.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/