On Fri, Mar 31, 2023 at 10:50:43AM -0400, Waiman Long <longman@xxxxxxxxxx> wrote:
By default, the clone(2) syscall spawn a child process into the sameShould .can_fork=cpuset_can_fork in analogy to cpuset_can_attach be also
cgroup as its parent. With the use of the CLONE_INTO_CGROUP flag
introduced by commit ef2c41cf38a7 ("clone3: allow spawning processes
into cgroups"), the child will be spawned into a different cgroup which
is somewhat similar to writing the child's tid into "cgroup.threads".
The current cpuset_fork() method does not properly handle the
CLONE_INTO_CGROUP case where the cpuset of the child may be different
from that of its parent. Update the cpuset_fork() method to treat the
CLONE_INTO_CGROUP case similar to cpuset_attach().
devised? (Sorry if I missed that in the previous discussion.)