linux-kernel - Re: Subject: Warning in workqueue.c

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 for Android: free password hash cracker in your pocket

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

Message-ID: <530B5EE3.8050200@linux.vnet.ibm.com>
Date:	Mon, 24 Feb 2014 10:01:55 -0500
From:	"Jason J. Herne" <jjherne@...ux.vnet.ibm.com>
To:	Tejun Heo <tj@...nel.org>, Peter Zijlstra <peterz@...radead.org>
CC:	Lai Jiangshan <laijs@...fujitsu.com>, linux-kernel@...r.kernel.org,
	Ingo Molnar <mingo@...hat.com>
Subject: Re: Subject: Warning in workqueue.c

On 02/14/2014 11:25 AM, Tejun Heo wrote:
> ...
> Hmmm... weird, p's rq shouldn't have changed without its cpus_allowed
> busted.  Anyways, let's wait for Jason's test results and see whether
> this is a regression at all.

I was unable to determine exactly when this behavior was introduced. The 
reason for this is because I keep hitting other bugs that prevent the 
test case from running, the most notable of which causes an immediate 
system hang. I also hit other warnings and bug messages and I'm not sure 
if they are related or if they will influence the probability of hitting 
the problem we are trying to solve here.  What I did find is the following:

We hit this problem as far back as v3.10.
The warning was introduced after v3.5 but before v3.6.

-- 
-- Jason J. Herne (jjherne@...ux.vnet.ibm.com)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/