From: Juri Lelli <juri.lelli@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Harshit Agarwal <harshit@nutanix.com>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
linux-kernel@vger.kernel.org, Jon Kohler <jon@nutanix.com>,
Gauri Patwardhan <gauri.patwardhan@nutanix.com>,
Rahul Chunduru <rahul.chunduru@nutanix.com>,
Will Ton <william.ton@nutanix.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v3] sched/rt: Fix race in push_rt_task
Date: Tue, 4 Mar 2025 16:18:09 +0000 [thread overview]
Message-ID: <Z8cnwcHxDxz1TmfL@jlelli-thinkpadt14gen4.remote.csb> (raw)
In-Reply-To: <20250304103001.0f89e953@gandalf.local.home>
On 04/03/25 10:30, Steven Rostedt wrote:
> On Tue, 4 Mar 2025 09:15:55 +0000
> Juri Lelli <juri.lelli@redhat.com> wrote:
>
> > As usual, we have essentially the same in deadline.c, do you think we
> > should/could implement the same fix proactively in there as well? Steve?
> >
>
> Probably. It would be better if we could find a way to consolidate the
> functionality so that when we fix a bug in one, the other gets fixed too.
That would be nice indeed.
Thanks,
Juri
next prev parent reply other threads:[~2025-03-04 16:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 18:05 Harshit Agarwal
2025-03-04 9:15 ` Juri Lelli
2025-03-04 15:30 ` Steven Rostedt
2025-03-04 16:18 ` Juri Lelli [this message]
2025-03-04 18:31 ` Harshit Agarwal
2025-03-04 18:31 ` Harshit Agarwal
2025-03-04 18:37 ` Harshit Agarwal
2025-03-05 10:43 ` Juri Lelli
2025-03-07 20:54 ` Harshit Agarwal
2025-03-04 18:57 ` Harshit Agarwal
2025-03-26 18:31 ` Phil Auld
2025-04-02 12:47 ` Peter Zijlstra
2025-04-08 19:05 ` [tip: sched/core] " tip-bot2 for Harshit Agarwal
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=Z8cnwcHxDxz1TmfL@jlelli-thinkpadt14gen4.remote.csb \
--to=juri.lelli@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=gauri.patwardhan@nutanix.com \
--cc=harshit@nutanix.com \
--cc=jon@nutanix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rahul.chunduru@nutanix.com \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=william.ton@nutanix.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®