From: Juri Lelli <juri.lelli@redhat.com>
To: Tejun Heo <tj@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Valentin Schneider <vschneid@redhat.com>,
K Prateek Nayak <kprateek.nayak@amd.com>,
Luca Abeni <luca.abeni@santannapisa.it>,
Andrea Righi <arighi@nvidia.com>,
sched-ext@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: sched/deadline: total_bw leak when a task leaves SCHED_DEADLINE while not queued
Date: Tue, 3 Nov 2026 12:29:40 +0100 [thread overview]
Message-ID: <aunFpOODCbZ9UtiE@jlelli-thinkpadt14gen4.remote.csb> (raw)
In-Reply-To: <0c5a32d85c3bf4d9fa3bacafa510b51f@kernel.org>
On 02/11/26 06:34, Tejun Heo wrote:
> Hello, Juri.
>
> On Mon, Nov 02, 2026 at 12:15:41PM +0100, Juri Lelli wrote:
> > Would you be able to re-test with the patches at
> >
> > https://github.com/jlelli/linux.git fix/dl-total-bw-leak
>
> On 473adf013e43, all three are fixed.
>
> Tested-by: Tejun Heo <tj@kernel.org>
>
> > BTW, it looks like I could verify with reproducers I pushed to
> > https://github.com/jlelli/sched-deadline-tests/commits/fix/dl-total-bw-leak-reproducer
> > but I'm not sure if they are similar/equivalent to what you have at your
> > end.
>
> They cover the same cases as mine.
Thanks for testing!
Series (including additional fixes) sent out as
20261103-b4-sched-dl-bw-fixes-v1-0-dd761fe005b4@redhat.com
Best,
Juri
prev parent reply other threads:[~2026-11-03 11:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 21:55 Tejun Heo
2026-10-30 9:22 ` Juri Lelli
2026-10-31 0:47 ` Tejun Heo
2026-11-02 10:08 ` Juri Lelli
2026-11-02 11:15 ` Juri Lelli
2026-11-02 16:34 ` Tejun Heo
2026-11-03 11:29 ` Juri Lelli [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=aunFpOODCbZ9UtiE@jlelli-thinkpadt14gen4.remote.csb \
--to=juri.lelli@redhat.com \
--cc=arighi@nvidia.com \
--cc=dietmar.eggemann@arm.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.abeni@santannapisa.it \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sched-ext@lists.linux.dev \
--cc=tj@kernel.org \
--cc=vincent.guittot@linaro.org \
--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
all inboxes | Powered by JetHome®