From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755286AbbLKPJm (ORCPT ); Fri, 11 Dec 2015 10:09:42 -0500 Received: from bombadil.infradead.org ([198.137.202.9]:46085 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753711AbbLKPJh (ORCPT ); Fri, 11 Dec 2015 10:09:37 -0500 Date: Fri, 11 Dec 2015 16:09:26 +0100 From: Peter Zijlstra To: Alexander Shishkin Cc: Ingo Molnar , linux-kernel@vger.kernel.org, vince@deater.net, eranian@google.com, Arnaldo Carvalho de Melo , Mathieu Poirier Subject: Re: [PATCH v0 3/5] perf: Introduce instruction trace filtering Message-ID: <20151211150926.GV6356@twins.programming.kicks-ass.net> References: <1449840998-29902-1-git-send-email-alexander.shishkin@linux.intel.com> <1449840998-29902-4-git-send-email-alexander.shishkin@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1449840998-29902-4-git-send-email-alexander.shishkin@linux.intel.com> User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Dec 11, 2015 at 03:36:36PM +0200, Alexander Shishkin wrote: > @@ -559,6 +590,10 @@ struct perf_event { > > atomic_t event_limit; > > + /* instruction trace filters */ > + struct list_head itrace_filters; > + struct mutex itrace_filters_mutex; > + > void (*destroy)(struct perf_event *); > struct rcu_head rcu_head; > > +static int __perf_event_itrace_filters_setup(void *info) > +{ > + struct perf_event *event = info; > + int ret; > + > + if (READ_ONCE(event->state) != PERF_EVENT_STATE_ACTIVE) > + return -EAGAIN; > + > + /* matches smp_wmb() in event_sched_in() */ > + smp_rmb(); > + > + /* > + * There is a window with interrupts enabled before we get here, > + * so we need to check again lest we try to stop another cpu's event. > + */ > + if (READ_ONCE(event->oncpu) != smp_processor_id()) > + return -EAGAIN; > + > + event->pmu->stop(event, PERF_EF_UPDATE); > + rcu_read_lock(); So you're holding rcu_read_lock() here to ensure the filter list is observable. However this is still very much racy, nothing stops another filter being added while we're trying to validate/program the hardware. The solution we've used for other such places in perf is to use both a mutex and a spinlock to protect the list. You need to hold both to modify a list, holding either ensures the list is stable. That would allow you to hold the spinlock here, and call the pmu method on a stable list. > + ret = event->pmu->itrace_filter_setup(event); > + rcu_read_unlock(); > + event->pmu->start(event, PERF_EF_RELOAD); > + > + return ret; > +} > +/* > + * Insert an itrace @filter into @event's list of filters. > + * @filter is used as a template > + */ > +static int perf_itrace_filter_insert(struct perf_event *event, > + struct perf_itrace_filter *src, > + struct task_struct *task) > +{ > + /* > + * If we're called through perf_itrace_filters_clone(), we're already > + * holding parent's filter mutex. > + */ > + mutex_lock_nested(&event->itrace_filters_mutex, SINGLE_DEPTH_NESTING); > + list_add_tail_rcu(&filter->entry, &event->itrace_filters); > + mutex_unlock(&event->itrace_filters_mutex); > + > + return 0; > +}