mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guopeng Zhang <guopeng.zhang@linux.dev>
To: Waiman Long <longman@redhat.com>, Tejun Heo <tj@kernel.org>,
	Ridong Chen <ridong.chen@linux.dev>
Cc: "Johannes Weiner" <hannes@cmpxchg.org>,
	"Michal Koutný" <mkoutny@suse.com>,
	cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Guopeng Zhang" <zhangguopeng@kylinos.cn>
Subject: Re: [PATCH 0/2] cgroup/cpuset: Fix partition updates using stale CPU masks
Date: Tue, 20 Oct 2026 10:51:05 +0800	[thread overview]
Message-ID: <56d84287-3de3-4a57-a92f-ca63d6dcda96@linux.dev> (raw)
In-Reply-To: <20261010075947.333549-1-guopeng.zhang@linux.dev>

Hello,Longman

Could you take a look at this patch series when you have a chance?

Thanks,
Guopeng

在 2026/10/10 15:59, Guopeng Zhang 写道:
> From: Guopeng Zhang <zhangguopeng@kylinos.cn>
> 
> These patches fix two cases where partition updates read stale configured
> CPU masks:
> 
> 1. Shrinking cpuset.cpus of a remote partition can leave a removed CPU
>    unavailable to the top cpuset.
> 2. Updating cpuset.cpus.exclusive can leave an invalid local partition
>    unable to recover after the mask becomes valid.
> 
> Move each configured mask update before partition_cpus_change().
> 
> Guopeng Zhang (2):
>   cgroup/cpuset: Fix cpuset.cpus update in a remote partition
>   cgroup/cpuset: Fix invalid local partition recovery
> 
>  kernel/cgroup/cpuset.c | 11 +++++++++--
>  1 file changed, 9 insertions(+), 2 deletions(-)
> 


      parent reply	other threads:[~2026-10-20  2:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-10  7:59 Guopeng Zhang
2026-10-10  7:59 ` [PATCH 1/2] cgroup/cpuset: Fix cpuset.cpus update in a remote partition Guopeng Zhang
2026-10-10  7:59 ` [PATCH 2/2] cgroup/cpuset: Fix invalid local partition recovery Guopeng Zhang
2026-10-20  2:51 ` Guopeng Zhang [this message]

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=56d84287-3de3-4a57-a92f-ca63d6dcda96@linux.dev \
    --to=guopeng.zhang@linux.dev \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mkoutny@suse.com \
    --cc=ridong.chen@linux.dev \
    --cc=tj@kernel.org \
    --cc=zhangguopeng@kylinos.cn \
    /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
all inboxes | Powered by JetHome®