Re: [PATCH REPOST v3.9-rc1] sched: replace PF_THREAD_BOUND with PF_NO_SETAFFINITY

2013-03-19 Thread Tejun Heo
On Mon, Mar 18, 2013 at 09:47:15AM -0700, Tejun Heo wrote: > Hello, > > On Mon, Mar 18, 2013 at 10:41:40AM +0100, Ingo Molnar wrote: > > > This patch replaces PF_THREAD_BOUND with PF_NO_SETAFFINITY. > > > sched_setaffinity() checks the flag and return -EINVAL if set. > > > set_cpus_allowed_ptr() i

Re: [PATCH REPOST v3.9-rc1] sched: replace PF_THREAD_BOUND with PF_NO_SETAFFINITY

2013-03-18 Thread Tejun Heo
Hello, On Mon, Mar 18, 2013 at 10:41:40AM +0100, Ingo Molnar wrote: > > This patch replaces PF_THREAD_BOUND with PF_NO_SETAFFINITY. > > sched_setaffinity() checks the flag and return -EINVAL if set. > > set_cpus_allowed_ptr() is no longer affected by the flag. > > > > This will allow simplifying

Re: [PATCH REPOST v3.9-rc1] sched: replace PF_THREAD_BOUND with PF_NO_SETAFFINITY

2013-03-18 Thread Ingo Molnar
* Tejun Heo wrote: > PF_THREAD_BOUND was originally used to mark kernel threads which were > bound to a specific CPU using kthread_bind() and a task with the flag > set allows cpus_allowed modifications only to itself. Workqueue is > currently abusing it to prevent userland from meddling with >

[PATCH REPOST v3.9-rc1] sched: replace PF_THREAD_BOUND with PF_NO_SETAFFINITY

2013-03-14 Thread Tejun Heo
PF_THREAD_BOUND was originally used to mark kernel threads which were bound to a specific CPU using kthread_bind() and a task with the flag set allows cpus_allowed modifications only to itself. Workqueue is currently abusing it to prevent userland from meddling with cpus_allowed of workqueue worke