From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yw0-x241.google.com (mail-yw0-x241.google.com [IPv6:2607:f8b0:4002:c05::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 3rVtx95pqPzDqdS for ; Fri, 17 Jun 2016 05:39:09 +1000 (AEST) Received: by mail-yw0-x241.google.com with SMTP id b75so6525577ywe.1 for ; Thu, 16 Jun 2016 12:39:09 -0700 (PDT) Date: Thu, 16 Jun 2016 15:39:05 -0400 From: Tejun Heo To: Peter Zijlstra Cc: Michael Ellerman , Gautham R Shenoy , Thomas Gleixner , Abdul Haleem , Aneesh Kumar , linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 2/2] workqueue:Fix affinity of an unbound worker of a node with 1 online CPU Message-ID: <20160616193905.GC3262@mtj.duckdns.org> References: <20160614112234.GF30154@twins.programming.kicks-ass.net> <20160615101936.GA31671@in.ibm.com> <20160615113249.GH30909@twins.programming.kicks-ass.net> <20160615125033.GB31671@in.ibm.com> <20160615131415.GI30909@twins.programming.kicks-ass.net> <20160615160112.GC24102@mtj.duckdns.org> <1466079084.19127.2.camel@ellerman.id.au> <20160616124548.GE30921@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20160616124548.GE30921@twins.programming.kicks-ass.net> List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, Jun 16, 2016 at 02:45:48PM +0200, Peter Zijlstra wrote: > Subject: workqueue: Fix setting affinity of unbound worker threads > From: Peter Zijlstra > Date: Thu Jun 16 14:38:42 CEST 2016 > > With commit e9d867a67fd03ccc ("sched: Allow per-cpu kernel threads to > run on online && !active"), __set_cpus_allowed_ptr() expects that only > strict per-cpu kernel threads can have affinity to an online CPU which > is not yet active. > > This assumption is currently broken in the CPU_ONLINE notification > handler for the workqueues where restore_unbound_workers_cpumask() > calls set_cpus_allowed_ptr() when the first cpu in the unbound > worker's pool->attr->cpumask comes online. Since > set_cpus_allowed_ptr() is called with pool->attr->cpumask in which > only one CPU is online which is not yet active, we get the following > WARN_ON during an CPU online operation. Applied to wq/for-4.7-fixes. Thanks. -- tejun