From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751797AbdEATvD (ORCPT ); Mon, 1 May 2017 15:51:03 -0400 Received: from mail-yw0-f172.google.com ([209.85.161.172]:34057 "EHLO mail-yw0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750945AbdEATvB (ORCPT ); Mon, 1 May 2017 15:51:01 -0400 Date: Mon, 1 May 2017 15:50:58 -0400 From: Tejun Heo To: Steven Rostedt Cc: "Paul E. McKenney" , jiangshanlai@gmail.com, linux-kernel@vger.kernel.org Subject: Re: WARN_ON_ONCE() in process_one_work()? Message-ID: <20170501195058.GH8921@htj.duckdns.org> References: <20170501165747.GA993@linux.vnet.ibm.com> <20170501184250.GA8921@htj.duckdns.org> <20170501154237.71ba2d28@gandalf.local.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170501154237.71ba2d28@gandalf.local.home> User-Agent: Mutt/1.8.0 (2017-02-23) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, May 01, 2017 at 03:42:37PM -0400, Steven Rostedt wrote: > 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. Were you also using nohz_full? Thanks. -- tejun