public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Ankit Jain <ankitja@vmware.com>
Cc: juri.lelli@redhat.com, bristot@redhat.com,
	l.stach@pengutronix.de, suhui_kernel@163.com,
	msimmons@redhat.com, peterz@infradead.org, glenn@aurora.tech,
	stable@vger.kernel.org, linux-kernel@vger.kernel.org,
	srivatsab@vmware.com, srivatsa@csail.mit.edu, akaher@vmware.com,
	amakhalov@vmware.com, vsirnapalli@vmware.com,
	sturlapati@vmware.com, bordoloih@vmware.com,
	keerthanak@vmware.com
Subject: Re: [PATCH v4.19.y 0/4] sched/deadline: Fix panic due to nested priority inheritance
Date: Thu, 25 Aug 2022 14:31:10 +0200	[thread overview]
Message-ID: <Ywdrjqht7agq0WrY@kroah.com> (raw)
In-Reply-To: <20220822074348.218135-1-ankitja@vmware.com>

On Mon, Aug 22, 2022 at 01:13:44PM +0530, Ankit Jain wrote:
> When a CFS task that was boosted by a SCHED_DEADLINE
> task boosts another CFS task (nested priority inheritance),
> Kernel panic is observed.
> Fixing priority inheritance changes the way how sched_deadline
> attributes are being inherited from original donor task.
> 
> Additional supporting patches are added to fix throttling of
> boosted tasks.
> 
> Daniel Bristot de Oliveira (1):
>   sched/deadline: Unthrottle PI boosted threads while enqueuing
> 
> Lucas Stach (1):
>   sched/deadline: Fix stale throttling on de-/boosted tasks
> 
> Juri Lelli (1):
>   sched/deadline: Fix priority inheritance with multiple scheduling
>     classes
> 
> Hui Su (1):
>   kernel/sched: Remove dl_boosted flag comment
> 
>  include/linux/sched.h   |  13 ++--
>  kernel/sched/core.c     |  11 ++--
>  kernel/sched/deadline.c | 131 +++++++++++++++++++++++++---------------
>  3 files changed, 96 insertions(+), 59 deletions(-)
> 
> -- 
> 2.34.1
> 

Both sets of backports now queued up, thanks.

greg k-h

      parent reply	other threads:[~2022-08-25 12:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-22  7:43 [PATCH v4.19.y 0/4] sched/deadline: Fix panic due to nested priority inheritance Ankit Jain
2022-08-22  7:43 ` [PATCH v4.19.y 1/4] sched/deadline: Unthrottle PI boosted threads while enqueuing Ankit Jain
2022-08-22  7:43 ` [PATCH v4.19.y 2/4] sched/deadline: Fix stale throttling on de-/boosted tasks Ankit Jain
2022-08-22  7:43 ` [PATCH v4.19.y 3/4] sched/deadline: Fix priority inheritance with multiple scheduling classes Ankit Jain
2022-08-22  7:43 ` [PATCH v4.19.y 4/4] kernel/sched: Remove dl_boosted flag comment Ankit Jain
2022-08-25 12:31 ` 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=Ywdrjqht7agq0WrY@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akaher@vmware.com \
    --cc=amakhalov@vmware.com \
    --cc=ankitja@vmware.com \
    --cc=bordoloih@vmware.com \
    --cc=bristot@redhat.com \
    --cc=glenn@aurora.tech \
    --cc=juri.lelli@redhat.com \
    --cc=keerthanak@vmware.com \
    --cc=l.stach@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=msimmons@redhat.com \
    --cc=peterz@infradead.org \
    --cc=srivatsa@csail.mit.edu \
    --cc=srivatsab@vmware.com \
    --cc=stable@vger.kernel.org \
    --cc=sturlapati@vmware.com \
    --cc=suhui_kernel@163.com \
    --cc=vsirnapalli@vmware.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