public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jari Ruusu <jariruusu@protonmail.com>
Cc: Sasha Levin <sashal@kernel.org>, Jon Kohler <jon@nutanix.com>,
	Rahul Chunduru <rahul.chunduru@nutanix.com>,
	Harshit Agarwal <harshit@nutanix.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: "sched/rt: Fix race in push_rt_task" linux kernel patch backports
Date: Wed, 28 Jan 2026 09:36:49 +0100	[thread overview]
Message-ID: <2026012823-displace-tattered-93cf@gregkh> (raw)
In-Reply-To: <V2MM9ljyF6PGt5ucnQnEfINZwUruiYJjACLxA1GVPpyG86xTZNhBEgG3wnglqW-mk6I-jx3pHU5w92fuw4drtmZqx7WGRQvXmClB1o8IuXo=@protonmail.com>

On Wed, Jan 28, 2026 at 07:38:25AM +0000, Jari Ruusu wrote:
> Jari Ruusu <jariruusu@protonmail.com> wrote:                                 
> >> Sorry to bother you with this question, but subject line mentioned linux 
> >> kernel patch (upstream commit 690e47d1403e90b7f2366f03b52ed3304194c793) 
> >> seems to be in 6.18.y and 6.12.y kernel branches, but does not seem 
> >> be backported to older stable branches such as 6.6.y and 6.1.y . 
> >> 
> >> To me, that patch you authored seems to be critically important, and 
> >> older kernel branches appear to have exact same race, but I am not 
> >> an expert on this, so I am asking you. 
> >> 
> >> Should that "sched/rt: Fix race in push_rt_task" patch be backported 
> >> to older stable kernel branches too? 
> >> 
> >> If, in your opinion, that patch should be backported to older stable 
> >> branches, is there any chance of you pinging Greg Kroah-Hartman 
> >> and Sasha Levin about it? 
>  
> Harshit Agarwal <harshit@nutanix.com> wrote:
> > Yes, the fix is applicable to older branches that you mentioned.
> > In fact I see that they ported my similar fix in the deadline   
> > scheduler to 6.1.x and 6.6.x.
> >
> > If you don't see the rt fix then can you please reach out to them and
> > feel free to add me to the thread?
>  
> Greg, Sasha,
>  
> Important upstream "sched/rt: Fix race in push_rt_task", commit
> 690e47d1403e90b7f2366f03b52ed3304194c793, is present in 6.18.y
> and 6.12.y kernel branches, but seems to be missing from older
> kernel branches.
>  
> Any chance backporting that race fix to older kernel branches?

It does not apply cleanly to older kernel branches.  So if it is needed
there, please provide a working backport and we will be glad to consider
it.

thanks,

greg k-h

  reply	other threads:[~2026-01-28  8:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <XNwjswArd6suoSJpq-8uKYzVza0e2t5b3LbInvmxCp4YxBq0Ugf-kGlnlzPY4tbrl5cvYkt3HedIcJPn_dq8-vs-egOj2aqdj0HbWbUQLiQ=@protonmail.com>
     [not found] ` <509103F3-EF26-48E9-8D65-79F269516BEE@nutanix.com>
2026-01-28  7:38   ` "sched/rt: Fix race in push_rt_task" linux kernel patch backports Jari Ruusu
2026-01-28  8:36     ` Greg Kroah-Hartman [this message]
2026-01-28 12:02       ` Jari Ruusu
2026-01-28 12:23         ` Greg Kroah-Hartman
2026-01-28 13:35           ` Jari Ruusu
2026-02-03 16:32             ` Greg Kroah-Hartman

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=2026012823-displace-tattered-93cf@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=harshit@nutanix.com \
    --cc=jariruusu@protonmail.com \
    --cc=jon@nutanix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rahul.chunduru@nutanix.com \
    --cc=sashal@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