From: Greg KH <greg@kroah.com>
To: Andrea Righi <arighi@nvidia.com>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
Tejun Heo <tj@kernel.org>, David Vernet <void@manifault.com>,
Changwoo Min <changwoo@igalia.com>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>
Subject: Re: Patch "sched_ext: Fix missing rq lock in scx_bpf_cpuperf_set()" has been added to the 6.14-stable tree
Date: Tue, 20 May 2025 10:51:27 +0200 [thread overview]
Message-ID: <2025052016-breeching-chastity-7935@gregkh> (raw)
In-Reply-To: <aCn2soZgtO3kWAyX@gpd3>
On Sun, May 18, 2025 at 05:03:14PM +0200, Andrea Righi wrote:
> Hi,
>
> On Sun, May 18, 2025 at 06:35:28AM -0400, Sasha Levin wrote:
> > This is a note to let you know that I've just added the patch titled
> >
> > sched_ext: Fix missing rq lock in scx_bpf_cpuperf_set()
> >
> > to the 6.14-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > sched_ext-fix-missing-rq-lock-in-scx_bpf_cpuperf_set.patch
> > and it can be found in the queue-6.14 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
>
> This requires upstream commit 18853ba782bef ("sched_ext: Track currently
> locked rq").
Thanks, I've dropped this from both queues now.
greg k-h
prev parent reply other threads:[~2025-05-20 8:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250518103528.1830160-1-sashal@kernel.org>
2025-05-18 15:03 ` Patch "sched_ext: Fix missing rq lock in scx_bpf_cpuperf_set()" has been added to the 6.14-stable tree Andrea Righi
2025-05-20 8:51 ` Greg KH [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=2025052016-breeching-chastity-7935@gregkh \
--to=greg@kroah.com \
--cc=arighi@nvidia.com \
--cc=bsegall@google.com \
--cc=changwoo@igalia.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tj@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=void@manifault.com \
--cc=vschneid@redhat.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