On Sun, Jun 12, 2022 at 10:53:53PM -0400, Waiman Long wrote: > Without this patch, cpus.effective will never be empty. It just falls back > to its parent if it becomes empty. Now with an empty cpus.effective, I am Yeah, that part is fine. > afraid that if a task is somehow moved to such a cpuset, something bad may > happen. So I add this check as a safeguard. But how would that happen? A lot of other things would break too if that were to happen. Thanks. -- tejun
