From: Venkat Rao Bagalkote <venkat88@linux.vnet.ibm.com>
To: Mike Galbraith <efault@gmx.de>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
peterz@infradead.org, vschneid@redhat.com, mingo@kernel.org,
sfr@canb.auug.org.au
Subject: Re: [patch] Re: [PowerPC][Linux-next][6.11.0-rc4-next-20240820] OOPs while running LTP FS Stress
Date: Thu, 19 Sep 2024 20:09:25 +0530 [thread overview]
Message-ID: <c8c28050-8c6e-45b1-8b70-06cf5e0921e6@linux.vnet.ibm.com> (raw)
In-Reply-To: <2fb24ab402d9de45e3cf16e6ba0ad23a7843e5c1.camel@gmx.de>
Hello Mike,
Thanks for the patch. I applied your patch and verified the issue, and
can confirm your patch fixes the issue.
Please add the below tags.
Reported-by: Venkat Rao Bagalkote <venkat88@linux.vnet.ibm.com>
Tested-by: Venkat Rao Bagalkote <venkat88@linux.vnet.ibm.com>
Regards,
Venkat.
On 19/09/24 11:39 am, Mike Galbraith wrote:
> On Mon, 2024-09-16 at 12:00 +0530, Venkat Rao Bagalkote wrote:
>> Greetings!!!
> Greetings,
>
>> I am seeing below kernel crash from 6.11.0-rc4-next-20240820.
>>
>>
>> Tried to do git bisect, but it didnt point to right patch. Attached is
>> the bisect log.
>>
>> Any help in fixing this is much appriciated.
> I met this, as well as other ways the wheels can fall off that turned
> out to have the same root. I gave Peter a heads up with diag offline,
> but having now convinced myself that all is well, I'll go ahead and
> post a patchlet.
>
> At the very least it's worth putting out for wider testing.. and should
> anyone have something prettier in mind, yeah, do that instead.
>
> sched: Fix sched_delayed vs cfs_bandwidth
>
> Meeting an unfinished DELAY_DEQUEUE treated entity in unthrottle_cfs_rq()
> leads to a couple terminal scenarios. Finish it first, so ENQUEUE_WAKEUP
> can proceed as it would have sans DELAY_DEQUEUE treatment.
>
> Fixes: 152e11f6df29 ("sched/fair: Implement delayed dequeue")
> Signed-off-by: Mike Galbraith <efault@gmx.de>
> ---
> kernel/sched/fair.c | 10 +++++++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
>
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -6049,10 +6049,14 @@ void unthrottle_cfs_rq(struct cfs_rq *cf
> for_each_sched_entity(se) {
> struct cfs_rq *qcfs_rq = cfs_rq_of(se);
>
> - if (se->on_rq) {
> - SCHED_WARN_ON(se->sched_delayed);
> - break;
> + /* Handle any unfinished DELAY_DEQUEUE business first. */
> + if (unlikely(se->on_rq && se->sched_delayed)) {
> + int flags = DEQUEUE_SLEEP | DEQUEUE_SPECIAL;
> +
> + dequeue_entity(qcfs_rq, se, flags | DEQUEUE_DELAYED);
> }
> + if (se->on_rq)
> + break;
> enqueue_entity(qcfs_rq, se, ENQUEUE_WAKEUP);
>
> if (cfs_rq_is_idle(group_cfs_rq(se)))
>
>
next prev parent reply other threads:[~2024-09-19 14:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 6:30 [PowerPC][Linux-next][6.11.0-rc4-next-20240820] OOPs while running LTP FS Stress Venkat Rao Bagalkote
2024-09-16 11:30 ` Peter Zijlstra
2024-09-16 14:40 ` Venkat Rao Bagalkote
2024-09-19 6:09 ` [patch] " Mike Galbraith
2024-09-19 14:39 ` Venkat Rao Bagalkote [this message]
2024-09-20 2:15 ` Mike Galbraith
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=c8c28050-8c6e-45b1-8b70-06cf5e0921e6@linux.vnet.ibm.com \
--to=venkat88@linux.vnet.ibm.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=vschneid@redhat.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