All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michal Koutný" <mkoutny@suse.com>
To: Tejun Heo <tj@kernel.org>,
	cgroups@vger.kernel.org,  linux-kernel@vger.kernel.org
Cc: Dan Schatzberg <dschatzberg@meta.com>,
	 Peter Zijlstra <peterz@infradead.org>,
	stable@vger.kernel.org, Noah Elias Feldt <N.Feldt@mittwald.de>,
	 Salvatore Bonaccorso <carnil@debian.org>,
	Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [PATCH v2] cgroup: Avoid iteration of dying tasks with zero refcount
Date: Mon, 7 Sep 2026 19:07:07 +0200	[thread overview]
Message-ID: <ap7u0VaI7JVAIq7K@localhost.localdomain> (raw)
In-Reply-To: <20260907170345.45316-1-mkoutny@suse.com>

[-- Attachment #1: Type: text/plain, Size: 557 bytes --]

On Mon, Sep 07, 2026 at 07:03:44PM +0200, Michal Koutný <mkoutny@suse.com> wrote:
> cgroup_task_release() is not synced via css_set_lock hence the race
> possibility. (I'm not 100% convinced about this LLM-assisted
> interleaving, multiple css_task_iter_next() calls may be involved with
> css_set_lock released.)

This paragraph should be editted out too because of

> Changes from v1 (https://lore.kernel.org/r/20260902161653.1051794-1-mkoutny@suse.com)
> - add css_set_lock release to sequence diagram

(Sorry for multi-messaging.)

Michal

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 265 bytes --]

  reply	other threads:[~2026-09-07 17:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-07 17:03 [PATCH v2] cgroup: Avoid iteration of dying tasks with zero refcount Michal Koutný
2026-09-07 17:07 ` Michal Koutný [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-09-07 19:27 Noah Feldt
2026-09-08 15:55 ` Michal Koutný
2026-09-11 16:11   ` Michal Koutný
2026-09-11 16:57     ` Tejun Heo

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=ap7u0VaI7JVAIq7K@localhost.localdomain \
    --to=mkoutny@suse.com \
    --cc=N.Feldt@mittwald.de \
    --cc=carnil@debian.org \
    --cc=cgroups@vger.kernel.org \
    --cc=dschatzberg@meta.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=stable@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.