From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753796AbeBGMG6 (ORCPT ); Wed, 7 Feb 2018 07:06:58 -0500 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:44714 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753535AbeBGMG4 (ORCPT ); Wed, 7 Feb 2018 07:06:56 -0500 Date: Wed, 7 Feb 2018 13:06:51 +0100 From: Jiri Olsa To: Steven Rostedt Cc: linux-kernel@vger.kernel.org, Linus Torvalds , Ingo Molnar , Andrew Morton , Thomas Gleixner , Peter Zijlstra , Masami Hiramatsu , Tom Zanussi , linux-rt-users@vger.kernel.org, linux-trace-users@vger.kernel.org, Arnaldo Carvalho de Melo , Clark Williams , Daniel Bristot de Oliveira , Juri Lelli , Jonathan Corbet , Mathieu Desnoyers , Namhyung Kim , Alexei Starovoitov Subject: Re: [PATCH 01/18] tracing: Add function based events Message-ID: <20180207120651.GB16048@krava> References: <20180202230458.840252014@goodmis.org> <20180202231017.160509978@goodmis.org> <20180205082423.GB1253@krava> <20180205100050.75c04497@gandalf.local.home> <20180206220917.1ca65b54@vmware.local.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180206220917.1ca65b54@vmware.local.home> User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Feb 06, 2018 at 10:09:17PM -0500, Steven Rostedt wrote: > On Mon, 5 Feb 2018 10:00:50 -0500 > Steven Rostedt wrote: > > > On Mon, 5 Feb 2018 09:24:23 +0100 > > Jiri Olsa wrote: > > > > > > > should this be done under 'func_event_mutex' ? > > > > Probably. > > I think we only need to add the list. yep, seems enough jirka > > > > > > > > > I tried and crashed the system by running 2 scripts with: > > > > > > echo 'ip_rcv(u64 skb, u64 dev)' > /sys/kernel/debug/tracing/function_events > > > echo 'SyS_openat(int dfd, string buf, x32 flags, x32 mode)' >> /sys/kernel/debug/tracing/function_events > > > echo 'SyS_open(x8[32] buf, x32 flags, x32 mode)' >> /sys/kernel/debug/tracing/function_events > > > > > > > There's no reason that we can't have more than one function event > attached to the same function. I'm adding this: > > diff --git a/kernel/trace/trace_event_ftrace.c b/kernel/trace/trace_event_ftrace.c > index b145639eac45..928168fc2025 100644 > --- a/kernel/trace/trace_event_ftrace.c > +++ b/kernel/trace/trace_event_ftrace.c > @@ -1275,12 +1275,6 @@ static int create_function_event(int argc, char **argv) > if (state != FUNC_STATE_END) > goto fail; > > - ret = -EALREADY; > - list_for_each_entry(fe, &func_events, list) { > - if (strcmp(fe->func, func_event->func) == 0) > - goto fail; > - } > - > ret = ftrace_set_filter(&func_event->ops, func_event->func, > strlen(func_event->func), 0); > if (ret < 0) > @@ -1290,7 +1284,9 @@ static int create_function_event(int argc, char **argv) > if (ret < 0) > goto fail; > > + mutex_lock(&func_event_mutex); > list_add_tail(&func_event->list, &func_events); > + mutex_unlock(&func_event_mutex); > return 0; > fail: > free_func_event(func_event); > > -- Steve