From: K Prateek Nayak <kprateek.nayak@amd.com>
To: "Luis Claudio R. Goncalves" <lgoncalv@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>, Phil Auld <pauld@redhat.com>,
"Valentin Schneider" <vschneid@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Shizhao Chen <shichen@redhat.com>, <linux-kernel@vger.kernel.org>,
Omar Sandoval <osandov@fb.com>,
Xuewen Yan <xuewen.yan@unisoc.com>
Subject: Re: sched: update_entity_lag does not handle corner case with task in PI chain
Date: Fri, 24 Oct 2025 09:30:02 +0530 [thread overview]
Message-ID: <1fa78304-b194-4d34-888a-c387859ef72d@amd.com> (raw)
In-Reply-To: <aPgm6KvDx5Os2oJS@uudg.org>
Hello Luis,
On 10/22/2025 6:05 AM, Luis Claudio R. Goncalves wrote:
>> v6.18 kernels will get rid of this issue as a part of per-task throttle
>> feature and stable should pick up the fix for same on the thread soon.
>
> Thank you! You were right, your patch in that thread seems to have fixed
> the issue I reported.
>
> I read the thread you mentioned, built a test kernel with the patch and have
> been running tests for more than 6h now without a single backtrace. As reported
> earlier, I was able to hit the bug within 15 minutes without the patch.
Thank you for confirming! Greg has picked the patches for both
v6.17 stable and v6.12 stable so the upcoming stable releases and the
RT releases based on them should solve this issues. Thank you again
for testing the fix.
--
Thanks and Regards,
Prateek
prev parent reply other threads:[~2025-10-24 4:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-18 11:34 Luis Claudio R. Goncalves
2025-10-18 19:57 ` Peter Zijlstra
2025-10-20 11:00 ` Luis Claudio R. Goncalves
2025-10-21 7:08 ` K Prateek Nayak
2025-10-22 0:35 ` Luis Claudio R. Goncalves
2025-10-24 4:00 ` K Prateek Nayak [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=1fa78304-b194-4d34-888a-c387859ef72d@amd.com \
--to=kprateek.nayak@amd.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=lgoncalv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=osandov@fb.com \
--cc=pauld@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=shichen@redhat.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=xuewen.yan@unisoc.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
all inboxes | Powered by JetHome®