[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <38470D92-7862-4921-A2D6-E8B37E15FBCD@nutanix.com>
Date: Tue, 4 Mar 2025 18:57:29 +0000
From: Harshit Agarwal <harshit@...anix.com>
To: Juri Lelli <juri.lelli@...hat.com>
CC: Steven Rostedt <rostedt@...dmis.org>, Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Vincent Guittot
<vincent.guittot@...aro.org>,
Dietmar Eggemann <dietmar.eggemann@....com>,
Ben Segall <bsegall@...gle.com>, Mel Gorman <mgorman@...e.de>,
Valentin
Schneider <vschneid@...hat.com>,
"linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>,
Jon Kohler <jon@...anix.com>,
Gauri
Patwardhan <gauri.patwardhan@...anix.com>,
Rahul Chunduru
<rahul.chunduru@...anix.com>,
Will Ton <william.ton@...anix.com>,
"stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: Re: [PATCH v3] sched/rt: Fix race in push_rt_task
Sorry for the repeat messages, my email client’s acting up. :)
> On Mar 4, 2025, at 8:18 AM, Juri Lelli <juri.lelli@...hat.com> wrote:
>
> !-------------------------------------------------------------------|
> CAUTION: External Email
>
> |-------------------------------------------------------------------!
>
> On 04/03/25 10:30, Steven Rostedt wrote:
>> On Tue, 4 Mar 2025 09:15:55 +0000
>> Juri Lelli <juri.lelli@...hat.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
>
Powered by blists - more mailing lists