On 11/27, zhang.y...@zte.com.cn wrote: > > Userspace process doesn't want the PF_NO_SETAFFINITY, but its parent may be > a kernel worker thread which has PF_NO_SETAFFINITY set, and this worker thread > can do kernel_thread() to create the child. > Clearing this flag in usersapce child to enable its migrating capability. > > > Signed-off-by: Zhang Yi <zhang.y...@zte.com.cn>
Thanks! Acked-by: Oleg Nesterov <o...@redhat.com> > --- linux-3.12.old/fs/exec.c 2013-11-26 08:53:12.175811856 +0000 > +++ linux-3.12/fs/exec.c 2013-11-27 09:36:56.231972168 +0000 > @@ -1090,8 +1090,8 @@ int flush_old_exec(struct linux_binprm * > bprm->mm = NULL; /* We're using it now */ > > set_fs(USER_DS); > - current->flags &= > - ~(PF_RANDOMIZE | PF_FORKNOEXEC | PF_KTHREAD | PF_NOFREEZE); > + current->flags &= ~(PF_RANDOMIZE | PF_FORKNOEXEC | PF_KTHREAD | > + PF_NOFREEZE | PF_NO_SETAFFINITY); > flush_thread(); > current->personality &= ~bprm->per_clear; > > -- 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/
