linux-kernel - Re: WARN_ON_ONCE() in process_one

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20170501195058.GH8921@htj.duckdns.org>
Date:   Mon, 1 May 2017 15:50:58 -0400
From:   Tejun Heo <tj@...nel.org>
To:     Steven Rostedt <rostedt@...dmis.org>
Cc:     "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
        jiangshanlai@...il.com, linux-kernel@...r.kernel.org
Subject: Re: WARN_ON_ONCE() in process_one_work()?

On Mon, May 01, 2017 at 03:42:37PM -0400, Steven Rostedt wrote:
> On Mon, 1 May 2017 14:42:50 -0400
> Tejun Heo <tj@...nel.org> 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