Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Luis Claudio R. Goncalves" <lgoncalv@redhat.com>
Cc: Sasha Levin <sashal@kernel.org>,
	stable@vger.kernel.org, stable-commits@vger.kernel.org,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Clark Williams <clrkwllms@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: Patch "sched: Do not call __put_task_struct() on rt if pi_blocked_on is set" has been added to the 6.16-stable tree
Date: Tue, 12 Aug 2025 10:55:51 +0200	[thread overview]
Message-ID: <2025081238-tiring-prelaunch-3338@gregkh> (raw)
In-Reply-To: <aJlFVnuKwSyDTXOq@uudg.org>

On Sun, Aug 10, 2025 at 10:20:22PM -0300, Luis Claudio R. Goncalves wrote:
> On Fri, Aug 08, 2025 at 07:27:26PM -0400, Sasha Levin wrote:
> > This is a note to let you know that I've just added the patch titled
> > 
> >     sched: Do not call __put_task_struct() on rt if pi_blocked_on is set
> > 
> > to the 6.16-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-do-not-call-__put_task_struct-on-rt-if-pi_bloc.patch
> > and it can be found in the queue-6.16 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.
> 
> Hi Sasha!
> 
> I am the author of that patch and I sent a follow-up patch that fixes a
> mistake I made on the original patch:
> 
>     [RESEND PATCH] sched: restore the behavior of put_task_struct() for non-rt
>     https://lore.kernel.org/all/aJOwe_ZS5rHXMrsO@uudg.org/
> 
> The patch you have does not match what is in the description. I unfortunately
> sent the wrong version of the patch on the verge of leaving for a long vacation
> and only noticed that when I returned. The code is correct, but does not
> match the commit description and is a change that I would like to propose
> later as an RFC, not the simpler bugfix originally intended.
> 
> I suggest waiting for the follow-up patch mentioned above to include both on
> stable kernels.

Ok, I'll go drop this now but please let us know when both patches
shoudl be added.

thanks,

greg k-h

      reply	other threads:[~2025-08-12  8:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250808232726.1423484-1-sashal@kernel.org>
2025-08-11  1:20 ` Patch "sched: Do not call __put_task_struct() on rt if pi_blocked_on is set" has been added to the 6.16-stable tree Luis Claudio R. Goncalves
2025-08-12  8:55   ` 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=2025081238-tiring-prelaunch-3338@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=bigeasy@linutronix.de \
    --cc=clrkwllms@kernel.org \
    --cc=lgoncalv@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=sashal@kernel.org \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.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