Re: [RESEND PATCH v4 10/17] sched/deadline: Fix an overflow of the 0-lag time with long periods

From: sashiko-bot

Date: Thu Nov 19 2026 - 11:47:02 EST


Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Medium] sched/deadline: unguarded overrun division in
task_non_contending()
--

commit d4e10a0b92da9c2b0b15604d4fa7ca96de8eadaf
Author: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>

sched/deadline: Fix an overflow of the 0-lag time with long periods

This commit uses mul_u64_u64_div_u64() to compute the 0-lag time in
task_non_contending() so that runtime * dl_period does not overflow s64
with long periods, and bounds the positive-runtime division when the
parameters were shrunk.

> diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c
> index d6d2657dcddd6..5e4aff28e9bcd 100644
> --- a/kernel/sched/deadline.c
> +++ b/kernel/sched/deadline.c
> @@ -411,7 +411,7 @@ static void task_non_contending(struct sched_dl_entity *dl_se, bool dl_task)
> struct hrtimer *timer = &dl_se->inactive_timer;
> struct rq *rq = rq_of_dl_se(dl_se);
> struct dl_rq *dl_rq = &rq->dl;
> - s64 zerolag_time;
> + s64 zerolag_time, left;
>
> /*
> * If this is a non-deadline task that has been boosted,
> @@ -425,15 +425,40 @@ static void task_non_contending(struct sched_dl_entity *dl_se, bool dl_task)
>
> WARN_ON(dl_se->dl_non_contending);
>
> - zerolag_time = dl_se->deadline -
> - div64_long((dl_se->runtime * dl_se->dl_period),
> - dl_se->dl_runtime);
> -
> /*
> - * Using relative times instead of the absolute "0-lag time"
> - * allows to simplify the code
> + * The 0-lag time is the deadline minus the runtime left, scaled by
> + * dl_period / dl_runtime. The product of the runtime and dl_period
> + * can overflow s64 with periods of a few seconds, so multiply on 128
> + * bits. Compute the 0-lag time relative to now.
> + *
> + * After a change of parameters, the runtime and the deadline stay
> + * those of the old parameters until the next period. The 0-lag time
> + * uses the new dl_runtime and dl_period. The runtime left can then be
> + * far above dl_runtime, and the quotient too large for 64 bits. So
> + * first compare the runtime left with the runtime that the new
> + * parameters give until the deadline:
> + *
> + * (deadline - now) * dl_runtime / dl_period
> + *
> + * If it is larger, the 0-lag time has passed, and the bandwidth is
> + * released now.
> + *
> + * The runtime is negative after an overrun. The next tick throttles
> + * the task, so the overrun is short and its quotient fits.
> */
> - zerolag_time -= rq_clock(rq);
> + left = dl_se->deadline - rq_clock(rq);
> + if (dl_se->runtime < 0)
> + zerolag_time = left +
> + mul_u64_u64_div_u64(-dl_se->runtime, dl_se->dl_period,
> + dl_se->dl_runtime);

[Severity: Medium]
Can mul_u64_u64_div_u64() in the dl_se->runtime < 0 branch still overflow
s64 or u64 when dl_runtime was shrunk or the overrun spans multiple
seconds?

An overrun is not guaranteed to be short: in a guest, a vCPU preemption
can produce a multi-second delta_exec in a single update_curr_dl_se()
call, and a task throttled while blocking on an rt_mutex that is then
PI-boosted before waking has dl_throttled cleared in enqueue_task_dl()
without replenishment (because dl_entity_overflow() returns false when
dl_se->runtime < 0).

If a task with a raised period limit (e.g. 300s or UINT_MAX us) shrinks
dl_runtime to 1024 ns via sched_setattr(), an overrun of a few seconds
makes (-dl_se->runtime * dl_se->dl_period) / dl_se->dl_runtime exceed
S64_MAX (wrapping zerolag_time negative and releasing bandwidth early) or
U64_MAX (trapping with #DE in divq on x86-64). Even with the default 4s
period limit, scaling a single-tick overrun of the old runtime by the new
dl_period / dl_runtime ratio can arm inactive_timer for hours, locking up
running_bw and total_bw.

--
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1795105408.git.mathieu.desnoyers@xxxxxxxxxxxx?part=10