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]
Date:	Thu, 25 Apr 2013 09:34:37 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Robin Holt <holt@....com>, "H. Peter Anvin" <hpa@...or.com>,
	"Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>,
	Russ Anderson <rja@....com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	the arch/x86 maintainers <x86@...nel.org>,
	Tejun Heo <tj@...nel.org>
Subject: Re: [PATCH -v6 2/5] Migrate shutdown/reboot to boot cpu.


* Andrew Morton <akpm@...ux-foundation.org> wrote:

> On Thu, 25 Apr 2013 08:57:04 +0200 Ingo Molnar <mingo@...nel.org> wrote:
> 
> > > PF_THREAD_BOUND was removed/replaced in linux-next's a9ab775bc
> > > ("workqueue: directly restore CPU affinity of workers from CPU_ONLINE")
> > 
> > I don't see PF_THREAD_BOUND being removed by commit a9ab775bc. Did you 
> > mean some other commit?
> 
> commit 14a40ffccd6163bbcd1d6f32b28a88ffe6149fc6
> Author: Tejun Heo <tj@...nel.org>
> Date:   Tue Mar 19 13:45:20 2013 -0700
> 
>     sched: replace PF_THREAD_BOUND with PF_NO_SETAFFINITY

I don't think much action is needed: whenever someone integrates the 
workqueue tree with these reboot changes, or the workqueue changes hit 
upstream, a s/PF_THREAD_BOUND/PF_NO_SETAFFINITY should do the trick, 
right?

Btw., if that's true then the workqueue tree should probably grow this 
helper:

	#define PF_THREAD_BOUND PF_NO_SETAFFINITY

migration/backport helper, which can be removed in v3.11 or so.

Thanks,

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

Powered by blists - more mailing lists