On 2/22/22 12:26, Tejun Heo wrote:
(cc'ing Waiman and quoting whole body) Hello, Waiman. It looks like it's hitting WARN_ON(!is_in_v2_mode() && !nodes_equal(cp->mems_allowed, cp->effective_mems)) Can you take a look?
My preliminary analysis is that the warning may be caused by my commit 1f1562fcd04a ("cgroup/cpuset: Don't let child cpusets restrict parent in default hierarchy") since the merge branch e5313968c41b is missing the fix commit d068eebbd482 ("cgroup/cpuset: Make child cpusets restrict parents on v1 hierarchy"). I believe the problem should be gone once the merge branch is updated to a later upstream baseline.
Cheers, Longman
