From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751827AbdEATmn (ORCPT ); Mon, 1 May 2017 15:42:43 -0400 Received: from mail.kernel.org ([198.145.29.136]:51078 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751327AbdEATmm (ORCPT ); Mon, 1 May 2017 15:42:42 -0400 Date: Mon, 1 May 2017 15:42:37 -0400 From: Steven Rostedt To: Tejun Heo Cc: "Paul E. McKenney" , jiangshanlai@gmail.com, linux-kernel@vger.kernel.org Subject: Re: WARN_ON_ONCE() in process_one_work()? Message-ID: <20170501154237.71ba2d28@gandalf.local.home> In-Reply-To: <20170501184250.GA8921@htj.duckdns.org> References: <20170501165747.GA993@linux.vnet.ibm.com> <20170501184250.GA8921@htj.duckdns.org> X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 1 May 2017 14:42:50 -0400 Tejun Heo wrote: > Steven's involved a rescuer too. One possibility was cpuset being > involved somehow and messing up the affinity of the rescuer kthread > unexpectedly. Is cpuset involved in any way? I didn't do anything with cpuset. I did take CPUs offline though. I'm currently testing changes, but when its done, I'll remove the "WARN_ON() comment out" and see if I can reproduce it again. -- Steve