From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
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,
Philo Lu <lulie@linux.alibaba.com>
Subject: Re: [PATCH 6.12.y 0/2] sched/psi: fix race in pressure_write (CVE-2026-52991)
Date: Sun, 19 Jul 2026 11:00:32 -0400 [thread overview]
Message-ID: <20260718192718.0018-stable-reply@kernel.org> (raw)
In-Reply-To: <9805cccf-91d8-4766-a79a-035e5de39857@linux.alibaba.com>
> 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.
A single combined patchset is fine when the same patches apply cleanly
to all the target trees - just list the versions in the subject like
you described. Separate per-tree submissions are only needed when the
backports diverge.
On this series: still holding for now - Tejun's fix for the psimon
creation under cgroup_mutex hasn't landed in mainline yet. Once it
does, I'll queue the series for 6.12, 6.6, and 6.1.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-07-19 15:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 8:32 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
2026-07-19 15:00 ` Sasha Levin [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=20260718192718.0018-stable-reply@kernel.org \
--to=sashal@kernel.org \
--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=lulie@linux.alibaba.com \
--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
Powered by JetHome