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: <20170614151548.GA14462@linux.vnet.ibm.com>
Date:   Wed, 14 Jun 2017 08:15:48 -0700
From:   "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:     Tejun Heo <tj@...nel.org>
Cc:     jiangshanlai@...il.com, linux-kernel@...r.kernel.org
Subject: Re: WARN_ON_ONCE() in process_one_work()?

On Tue, Jun 13, 2017 at 03:31:03PM -0700, Paul E. McKenney wrote:
> On Tue, Jun 13, 2017 at 04:58:37PM -0400, Tejun Heo wrote:
> > Hello, Paul.
> > 
> > On Fri, May 05, 2017 at 10:11:59AM -0700, Paul E. McKenney wrote:
> > > Just following up...  I have hit this bug a couple of times over the
> > > past few days.  Anything I can do to help?
> > 
> > My apologies for dropping the ball on this.  I've gone over the hot
> > plug code in workqueue several times but can't really find how this
> > would happen.  Can you please apply the following patch and see what
> > it says when the problem happens?
> 
> I have fired it up, thank you!
> 
> Last time I saw one failure in 21 hours of test runs, so I have kicked
> of 42 one-hour test runs.  Will see what happens tomorrow morning,
> Pacific Time.

And none of the 42 runs resulted in a workqueue splat.  I will try again
this evening, Pacific Time.

Who knows, maybe your diagnostic patch is the fix.  ;-)

							Thanx, Paul