Linux cgroups development
 help / color / mirror / Atom feed
From: Philo Lu <lulie@linux.alibaba.com>
To: Sasha Levin <sashal@kernel.org>, stable@vger.kernel.org
Cc: chenridong@huawei.com, tj@kernel.org, lizefan.x@bytedance.com,
	hannes@cmpxchg.org, cgroups@vger.kernel.org,
	linux-kernel@vger.kernel.org, eadavis@qq.com,
	chenridong@huaweicloud.com, akpm@linux-foundation.org,
	surenb@google.com, dust.li@linux.alibaba.com
Subject: Re: [PATCH 6.12.y 0/2] sched/psi: fix race in pressure_write (CVE-2026-52991)
Date: Fri, 17 Jul 2026 10:12:15 +0800	[thread overview]
Message-ID: <9805cccf-91d8-4766-a79a-035e5de39857@linux.alibaba.com> (raw)
In-Reply-To: <20260716232340.0009-stable-reply@kernel.org>


On 7/17/26 9:37 AM, Sasha Levin wrote:

> I'm holding off on this series (and the 6.6.y/6.1.y ones) for now: a5b98009f16d
> moves the psi trigger write path under cgroup_mutex, which means the psimon
> kthread gets created while holding cgroup_mutex and introduces a deadlock risk.
> 

Thanks for the heads-up, Sasha, and sorry I missed the patch you pointed 
out.

BTW, I have an unrelated question. I'd like to backport some stable 
patches to earlier LTS trees (e.g. from 6.18 down to 6.6). For patchsets 
like this one that apply cleanly to multiple versions (6.1, 6.6, and 
6.12), which of the following is preferred?

(1) A single patchset covering all three trees, with subjects like 
"[PATCH 6.1.y/6.6.y/6.12.y] ..."

(2) Three separate patchsets, one per stable tree.

Thanks.
-- 
Philo


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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-15  8:32 [PATCH 6.12.y 0/2] sched/psi: fix race in pressure_write (CVE-2026-52991) Philo Lu
2026-07-15  8:32 ` [PATCH 6.12.y 1/2] cgroup/psi: Set of->priv to NULL upon file release Philo Lu
2026-07-15  8:32 ` [PATCH 6.12.y 2/2] sched/psi: fix race between file release and pressure write Philo Lu
2026-07-17  1:37 ` [PATCH 6.12.y 0/2] sched/psi: fix race in pressure_write (CVE-2026-52991) Sasha Levin
2026-07-17  2:12   ` Philo Lu [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=9805cccf-91d8-4766-a79a-035e5de39857@linux.alibaba.com \
    --to=lulie@linux.alibaba.com \
    --cc=akpm@linux-foundation.org \
    --cc=cgroups@vger.kernel.org \
    --cc=chenridong@huawei.com \
    --cc=chenridong@huaweicloud.com \
    --cc=dust.li@linux.alibaba.com \
    --cc=eadavis@qq.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan.x@bytedance.com \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=surenb@google.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