From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757718AbcIHIAJ (ORCPT ); Thu, 8 Sep 2016 04:00:09 -0400 Received: from merlin.infradead.org ([205.233.59.134]:33540 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752056AbcIHIAH (ORCPT ); Thu, 8 Sep 2016 04:00:07 -0400 Date: Thu, 8 Sep 2016 09:59:55 +0200 From: Peter Zijlstra To: Srinivas Pandruvada Cc: rjw@rjwysocki.net, tglx@linutronix.de, mingo@redhat.com, bp@suse.de, x86@kernel.org, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org, tim.c.chen@linux.intel.com Subject: Re: [PATCH v2 5/8] sched,x86: Enable Turbo Boost Max Technology Message-ID: <20160908075955.GS10153@twins.programming.kicks-ass.net> References: <1472762024-88771-1-git-send-email-srinivas.pandruvada@linux.intel.com> <1472762024-88771-6-git-send-email-srinivas.pandruvada@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1472762024-88771-6-git-send-email-srinivas.pandruvada@linux.intel.com> User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Sep 01, 2016 at 01:33:41PM -0700, Srinivas Pandruvada wrote: > +static void enable_sched_itmt(bool enable_itmt) > +{ > + mutex_lock(&itmt_update_mutex); > + > + sysctl_sched_itmt_enabled = enable_itmt; > + x86_topology_update = true; > + rebuild_sched_domains(); > + > + mutex_unlock(&itmt_update_mutex); > +} > + > +static int sched_itmt_update_handler(struct ctl_table *table, int write, > + void __user *buffer, size_t *lenp, loff_t *ppos) > +{ > + int ret; > + > + ret = proc_dointvec_minmax(table, write, buffer, lenp, ppos); > + > + if (ret || !write) > + return ret; > + > + enable_sched_itmt(sysctl_sched_itmt_enabled); > + > + return ret; > +} I think there's a race here, if two tasks were to write to the sysctl they'd both change the value before getting stuck on the mutex in enable_sched_itmt(). One way around that is doing something like: struct ctl_table t; int val = sysctl_sched_itmt_enabled; t = *table; t.data = &val; proc_dointvec_minmax(&t, ...); /* and update the sysctl_sched_itmt_enabled value inside the mutex */ enable_sched_itmi(val);