[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZDb32V9xcWOi2_CL@slm.duckdns.org>
Date: Wed, 12 Apr 2023 08:26:33 -1000
From: Tejun Heo <tj@...nel.org>
To: Waiman Long <longman@...hat.com>
Cc: Zefan Li <lizefan.x@...edance.com>,
Johannes Weiner <hannes@...xchg.org>,
Christian Brauner <brauner@...nel.org>,
cgroups@...r.kernel.org, linux-kernel@...r.kernel.org,
Juri Lelli <juri.lelli@...hat.com>,
Dietmar Eggemann <dietmar.eggemann@....com>,
Michal Koutný <mkoutny@...e.com>,
Giuseppe Scrivano <gscrivan@...hat.com>
Subject: Re: [PATCH v4 0/5] cgroup/cpuset: Fix CLONE_INTO_CGROUP problem &
other issues
On Tue, Apr 11, 2023 at 09:35:56AM -0400, Waiman Long wrote:
> v4:
> - Add missing rcu_read_lock/unlock to cpuset_cancel_fork() in patch 3.
> - Add patch 5 to reduce performance impact for the
> non-CLONE_INTO_CGROUP case.
>
> v3:
> - Update patches 2 & 3 to put task_cs() call under rcu_read_lock().
>
> v2:
> - Drop v1 patch 3
> - Add a new patch to fix an issue in cpuset_cancel_attach() and
> another patch to add cpuset_can_fork() and cpuset_cacnel_fork()
> methods.
>
> The first patch in this series fixes a problem in
> cpuset_cancel_attach(). Patches 2 and 3 fixes the CLONE_INTO_CGROUP
> problem in cpuset. Patch 4 is a minor fix. The last patch is a
> performance optimization patch for the non-CLONE_INTO_CGROUP case.
Applied 1-4 to cgroup/for-6.3-fixes w/ stable cc'd. Given that the fixes are
a bit involved, the breakages have been there for quite a while and the
cpuset code has changed quite a bit, backporting might not be trivial tho.
Let's see how that goes.
Thanks.
--
tejun
Powered by blists - more mailing lists