mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Mukesh Ojha <quic_mojha@quicinc.com>
Cc: paulmck@kernel.org, lkml <linux-kernel@vger.kernel.org>,
	cgroups@vger.kernel.org, brauner@kernel.org, hannes@cmpxchg.org,
	shisiyuan <shisiyuan19870131@gmail.com>,
	"Li Zefan" <lizefan@huawei.com>,
	"Michal Koutný" <mkoutny@suse.com>
Subject: Re: [PATCH cgroup/for-5.19-fixes] cgroup: Use separate src/dst nodes when preloading css_sets for migration
Date: Thu, 16 Jun 2022 09:38:44 -1000	[thread overview]
Message-ID: <YquGxN1IWLegNyh6@slm.duckdns.org> (raw)
In-Reply-To: <Yqe4BjMZRohur3UM@slm.duckdns.org>

On Mon, Jun 13, 2022 at 12:19:50PM -1000, Tejun Heo wrote:
> Each cset (css_set) is pinned by its tasks. When we're moving tasks around
> across csets for a migration, we need to hold the source and destination
> csets to ensure that they don't go away while we're moving tasks about. This
> is done by linking cset->mg_preload_node on either the
> mgctx->preloaded_dst_csets or mgctx->preloaded_dst_csets list. Using the
> same cset->mg_preload_node for both the src and dst lists was deemed okay as
> a cset can't be both the source and destination at the same time.

Applied to cgroup/for-5.19-fixes w/ patch description fixed.

Thanks.

-- 
tejun

      parent reply	other threads:[~2022-06-16 19:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <549de740-1356-7ad2-3ee5-c52bc355fd99@quicinc.com>
2022-03-02 15:45 ` Use after free in cgroup_migrate_execute Tejun Heo
2022-05-16 14:54   ` Mukesh Ojha
2022-05-16 20:34     ` Paul E. McKenney
2022-06-13 15:25       ` Mukesh Ojha
2022-06-13 22:19         ` [PATCH cgroup/for-5.19-fixes] cgroup: Use separate src/dst nodes when preloading css_sets for migration Tejun Heo
2022-06-14 14:26           ` Christian Brauner
2022-06-16 19:38           ` Tejun Heo [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=YquGxN1IWLegNyh6@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=brauner@kernel.org \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=mkoutny@suse.com \
    --cc=paulmck@kernel.org \
    --cc=quic_mojha@quicinc.com \
    --cc=shisiyuan19870131@gmail.com \
    /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®