On Thu, Nov 28, 2013 at 12:45:42PM +0100, Oleg Nesterov wrote: > It has? khelper is a workqueue thread, this flag is set by create_worker(). > > And it does kernel_thread() (not kthread_create()) so the child gets this > flag too.
Urgh, but that's still completely wrong. khelper is a singlethread workqueue, those should be unbound and therefore should not have this flag set at all. In fact, I know people want to set affinity on khelper to ensure all the usermode helper tasks get spawned on the specific system-cpus and leave the rest of the system unperturbed. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
