From: Waiman Long <longman@redhat.com>
To: Tejun Heo <tj@kernel.org>, Zefan Li <lizefan.x@bytedance.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Christian Brauner <brauner@kernel.org>
Cc: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
Juri Lelli <juri.lelli@redhat.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
gscrivan@redhat.com, Waiman Long <longman@redhat.com>
Subject: [PATCH 0/3] cgroup/cpuset: Fix CLONE_INTO_CGROUP problem & other issues
Date: Fri, 31 Mar 2023 10:50:42 -0400 [thread overview]
Message-ID: <20230331145045.2251683-1-longman@redhat.com> (raw)
The first patch of this series fixes the incorrect cpumask problem
when the CLONE_INTO_CGROUP flag is used to clone a child to a different
cgroup. It also includes 2 other miscellaneous fixes to the cpuset code.
Waiman Long (3):
cgroup/cpuset: Make cpuset_fork() handle CLONE_INTO_CGROUP properly
cgroup/cpuset: Make cpuset_attach_task() skip subpartitions CPUs for
top_cpuset
cgroup/cpuset: Allow only one active attach operation per cpuset
kernel/cgroup/cpuset.c | 76 ++++++++++++++++++++++++++++--------------
1 file changed, 51 insertions(+), 25 deletions(-)
--
2.31.1
next reply other threads:[~2023-03-31 14:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 14:50 Waiman Long [this message]
2023-03-31 14:50 ` [PATCH 1/3] cgroup/cpuset: Make cpuset_fork() handle CLONE_INTO_CGROUP properly Waiman Long
[not found] ` <20230331145045.2251683-2-longman-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2023-04-03 16:55 ` Michal Koutný
2023-04-03 17:18 ` Waiman Long
[not found] ` <d9f0005c-6825-b2a0-eac3-fcbad6e32b2f-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2023-04-03 17:29 ` Waiman Long
2023-04-04 9:19 ` Michal Koutný
2023-04-04 13:52 ` Waiman Long
2023-04-04 17:26 ` Waiman Long
2023-04-06 9:45 ` Christian Brauner
2023-04-06 14:08 ` Waiman Long
2023-04-06 2:51 ` kernel test robot
[not found] ` <202304061003.e5e0dc9c-yujie.liu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2023-04-06 12:17 ` Waiman Long
[not found] ` <20230331145045.2251683-1-longman-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2023-03-31 14:50 ` [PATCH 2/3] cgroup/cpuset: Make cpuset_attach_task() skip subpartitions CPUs for top_cpuset Waiman Long
[not found] ` <20230331145045.2251683-3-longman-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2023-04-03 16:35 ` Michal Koutný
2023-03-31 14:50 ` [PATCH 3/3] cgroup/cpuset: Allow only one active attach operation per cpuset Waiman Long
[not found] ` <20230331145045.2251683-4-longman-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2023-04-03 16:47 ` Michal Koutný
2023-04-03 17:41 ` Waiman Long
[not found] ` <24b67530-62ce-4f9c-7b74-d41d2ccc710e-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2023-04-04 9:07 ` Michal Koutný
2023-04-04 14:12 ` Waiman Long
2023-04-06 9:44 ` Christian Brauner
2023-04-07 15:30 ` Waiman Long
[not found] ` <89853ab9-7759-11bf-f751-28ce81a4f02e-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2023-04-09 11:46 ` Christian Brauner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230331145045.2251683-1-longman@redhat.com \
--to=longman@redhat.com \
--cc=brauner@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=dietmar.eggemann@arm.com \
--cc=gscrivan@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox