Commit 0913b580f849 for kernel

commit 0913b580f8490caaaf08dd1591e0bc07ac2720cb
Merge: 50599e4c68ee 345f40166694
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed May 13 14:56:31 2026 -0700

    Merge tag 'cgroup-for-7.1-rc3-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup

    Pull cgroup fixes from Tejun Heo:

     - cpuset fixes:
         - Partition invalidation could return CPUs still in use by sibling
           partitions, producing overlapping effective_cpus
         - cpuset_can_attach() over-reserved DL bandwidth on moves that
           stayed within the same root domain
         - Pending DL migration state leaked into later attaches when a
           later can_attach() check failed
         - Reorder PF_EXITING and __GFP_HARDWALL checks so dying tasks can
           allocate from any node and exit quickly

     - dmem: propagate -ENOMEM instead of spinning forever when the fallback
       pool allocation also fails

     - selftests/cgroup: percpu test error-path leak, bogus numeric
       comparison of cpuset strings, and a zero-length read() that silently
       passed OOM-kill tests

    * tag 'cgroup-for-7.1-rc3-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup:
      cgroup/cpuset: Return only actually allocated CPUs during partition invalidation
      selftests/cgroup: Fix error path leaks in test_percpu_basic
      cgroup/cpuset: Reserve DL bandwidth only for root-domain moves
      cgroup/cpuset: Reset DL migration state on can_attach() failure
      selftests/cgroup: Fix string comparison in write_test
      selftests/cgroup: Fix cg_read_strcmp() empty string comparison
      cgroup/dmem: Return -ENOMEM on failed pool preallocation
      cgroup/cpuset: move PF_EXITING check before __GFP_HARDWALL in cpuset_current_node_allowed()