linux-kernel - Re: [PATCH] sched/kthread: Complain loudly when others violate our flags

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: <20110930085510.GA23868@mtj.dyndns.org>
Date:	Fri, 30 Sep 2011 01:55:10 -0700
From:	Tejun Heo <htejun@...il.com>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc:	Steven Rostedt <rostedt@...dmis.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] sched/kthread: Complain loudly when others violate our
 flags

Hello, Peter.

On Fri, Sep 30, 2011 at 10:34:59AM +0200, Peter Zijlstra wrote:
> On Thu, 2011-09-29 at 21:14 -0700, Tejun Heo wrote:
> > It's rather complicated due to the way workqueues have been used.  You
> > can't tell whether a work really needs to be pinned to one cpu for
> > correctness until actual cpu hotplug time as wq users are expected to
> > flush such work items from hotplug notifiers, so wq workers should be
> > pinned on the respective cpus while the cpus are up but also need to
> > step aside once unplug notifiers are finished. 
> 
> That really is crack, and I've always said so.
> 
> How about we fix that utter workqueue unplug nightmare..

The patch is corrupt (=20/=3D's).  Can you please re-send?

Thanks.

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