Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752814AbbEZKOV (ORCPT ); Tue, 26 May 2015 06:14:21 -0400 Received: from [85.118.1.10] ([85.118.1.10]:42052 "EHLO casper.infradead.org" rhost-flags-FAIL-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1752603AbbEZKOU (ORCPT ); Tue, 26 May 2015 06:14:20 -0400 Date: Tue, 26 May 2015 12:12:37 +0200 From: Peter Zijlstra To: Stephane Eranian Cc: Ingo Molnar , Vince Weaver , Jiri Olsa , "Liang, Kan" , LKML , Andrew Hunter , Maria Dimakopoulou Subject: Re: [PATCH v2 01/11] perf,x86: Fix event/group validation Message-ID: <20150526101237.GK3644@twins.programming.kicks-ass.net> References: <20150522132905.416122812@infradead.org> <20150522133135.353044581@infradead.org> <20150522134056.GG3644@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 Content-Length: 1942 Lines: 39 On Tue, May 26, 2015 at 02:24:38AM -0700, Stephane Eranian wrote: > On Fri, May 22, 2015 at 6:40 AM, Peter Zijlstra wrote: > > On Fri, May 22, 2015 at 03:29:06PM +0200, Peter Zijlstra wrote: > >> @@ -788,9 +788,9 @@ int x86_schedule_events(struct cpu_hw_ev > >> x86_pmu.start_scheduling(cpuc); > >> > >> for (i = 0, wmin = X86_PMC_IDX_MAX, wmax = 0; i < n; i++) { > >> + cpuc->event_constraint[i] = NULL; > > > > ^^^ that is new, which is esp. important in light of the > > intel_get_event_constraints() hunk below, which would happily continue > > life with a garbage constraint. > > > You've moved the constraint list from event to cpuc. Yet, it is still > an array of pointers > to constraints. So here you are saying, that in the case validate_group() is > preempted and there is a context switch, there is still a risk of > overwriting the > constraint? I don't see how because validate_group() is using a fake_cpuc. > So yes, the cpuc->event_constraint[] array is modified but it is not the same > as the actual cpuc used by non-validate code. Or am I still missing something? > > When using dynamic constraints, we already have constraint storage in cpuc > (to avoid calling kmalloc() in ctxsw context). Thus, I am wondering if it would > not be easier to always use cpuc for constraint storage (no more pointers). No; the problem here is repeated use of the cpuc (the real one). Say one scheduling run installs a constraint pointer for event i. Then event i gets removed and another installed in the same spot. Then the next scheduling run will pick up the old pointer in intel_get_event_constraints() as a base for the new one. -- 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/