From mboxrd@z Thu Jan 1 00:00:00 1970 From: Li Zefan Subject: Re: ftrace/perf_event leak Date: Wed, 01 Sep 2010 17:38:26 +0800 Message-ID: <4C7E1F12.8030304@cn.fujitsu.com> References: <4C7E11E5.1040402@redhat.com> <1283331868.2059.808.camel@laptop> <4C7E1C36.6070400@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Peter Zijlstra , Ingo Molnar , Frederic Weisbecker , Steven Rostedt , kvm-devel , Linux Kernel Mailing List To: Avi Kivity Return-path: In-Reply-To: <4C7E1C36.6070400@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org Avi Kivity wrote: > On 09/01/2010 12:04 PM, Peter Zijlstra wrote: >> >> Does something like the below cure that? >> > > Unfortunately not. > Then try this: The bug should be caused by commit 1c024eca51fdc965290acf342ae16a476c2189d0. --- diff --git a/kernel/trace/trace_event_perf.c b/kernel/trace/trace_event_perf.c index 8a2b73f..9d1d1f2 100644 --- a/kernel/trace/trace_event_perf.c +++ b/kernel/trace/trace_event_perf.c @@ -161,6 +161,7 @@ void perf_trace_destroy(struct perf_event *p_event) } } out: + module_put(tp_event->mod); mutex_unlock(&event_mutex); }