Re: [PATCH v9 16/33] sched/deadline: Keep the last CPU a task has in its root domain
From: Mathieu Desnoyers
Date: Fri Nov 20 2026 - 14:37:12 EST
> Can cpuset_offline_moves_dl() and cpuset_cpus_allowed_without() miss the
> invalidation of a sibling partition when an unpopulated parent partition
> delegates all of its active CPUs to child partitions?
Yes, by reading, for the tasks of c2. They change root domain with no
check for room when c2 and parent_p differ: one isolated, the other
not. The tasks of c1 are already checked. If c1 is not isolated, its
root domain loses its last CPU, and the offline is refused. If c1 is
isolated, the check of each task sees them leave the default root
domain.
v10 will model the cascade in both functions. partition_child_lost()
will take the child partition that cpuset makes invalid. That child
then counts as populated and holds no CPU. So the parent loses the
sibling partitions that cpuset makes invalid after it.
A new case, hotplug_sibling_partition_refused, will test your example.
The offline must fail with EBUSY. Without the fix, it is accepted.
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com