linux-kernel - Re: workqueue: WARN at at kernel/workqueue.c:2176

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: <53849EB7.9090302@linux.vnet.ibm.com>
Date:	Tue, 27 May 2014 10:18:31 -0400
From:	"Jason J. Herne" <jjherne@...ux.vnet.ibm.com>
To:	Peter Zijlstra <peterz@...radead.org>,
	Lai Jiangshan <laijs@...fujitsu.com>
CC:	Sasha Levin <sasha.levin@...cle.com>, Tejun Heo <tj@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Dave Jones <davej@...hat.com>, Ingo Molnar <mingo@...hat.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Steven Rostedt <rostedt@...dmis.org>
Subject: Re: workqueue: WARN at at kernel/workqueue.c:2176

On 05/16/2014 12:29 PM, Peter Zijlstra wrote:
> On Sat, May 17, 2014 at 12:18:06AM +0800, Lai Jiangshan wrote:
>> so the scheduler/set_cpus_allowed_ptr()/cpu_active_mask should be the first
>> place to fix.
>
> I'm not arguing about that, not to mention that this is userspace
> exposed and nobody protects that.
>
> But I was expecting kernel stuff that calls it on hotplug to be
> serialized thusly, but apparently not so.
>

Was a final patch posted for this issue? The discussion made it sound 
like there were still a few things to figure out before we could resolve 
this bug. I can recreate this as needed and I'm happy to test any patches.

-- 
-- 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/