From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=158.69.130.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1795105302; b=YCmncBale+cYeJF9g7f5uUPQ2yFpLn7vxG102A0PWWMi1HKPvSUFpfL4oHyGq8CJDm1I bngTKdSjD1spI6bl5jlXweUzubInQrkahPDEzSoYbJXDgKxQxmORc1K2HzN/sFYBGI6Hi n2mHsJaqv5skF8CTpQppsfplamdfuY18V/LYiK1q48U/a75lkq3zkLcrlAxbXnTDcofWF 6TE1XIzgIXCO96l1bnyhEGSKodSaOj7l0EpJHzMf0VvunEHjVp6Q0XNPdLJa4S7Inf+hP yRu/XcwBXaoCtWkUC9R6pbMPtDa5MRT0AngQw2EZRojhfBQ5UJre8RJYkyO+8B+c0oQ== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795105302; h=DMARC-Filter:DKIM-Signature:Received:From:To:Cc:Subject:Date: Message-Id:X-Mailer:In-Reply-To:References:MIME-Version: Content-Transfer-Encoding; bh=18ZdUzzadRsL6aFCNsE+0dn3GNsx1KvXA2R8ZIV+JwY=; b=GgKXifGDUiomsLrlkaA7G+GtckQVlaN3QonFC/9UboWOQK+QK/hO6vQnDtGNfpOqTtWz 3VnEBpj98gzmaaQTVcY9swkX8buTPMj8YUdQk0RJR6WRunGMuT33HaZ/r0bro2O6qB9ML UZa1EymITMp7p+ZWatN5FLhbCohE6BPzXf5+MmjZvSE7UJv0pGQUC0DXtQ7CpX1HwsLmV cvWzpXi8nBMaWUDojRu394ValHsVQx1AeasL7PRyeXbfhjwQ2/jyQTAm/nk50ogBSoW4H V6FkgZUpxtvXq3OF8kkwamUeQcnMEMn4PxlIUB16pQXo7wcEQazKXh4CIgJeeu3gC2Q== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass header.from=efficios.com; spf=pass smtp.mailfrom=efficios.com; dkim=pass header.d=efficios.com header.i=@efficios.com header.a=rsa-sha256 header.s=smtpout1 header.b=Pqv6Cq+M; arc=none smtp.remote-ip=158.69.130.18 Received: from smtpout.efficios.com (smtpout.efficios.com [158.69.130.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2FEEF60A2607; Thu, 19 Nov 2026 16:21:42 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.2 smtp.subspace.kernel.org 2FEEF60A2607 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=efficios.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=efficios.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=efficios.com header.i=@efficios.com header.a=rsa-sha256 header.s=smtpout1 header.b=Pqv6Cq+M DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=efficios.com; s=smtpout1; t=1795105300; bh=18ZdUzzadRsL6aFCNsE+0dn3GNsx1KvXA2R8ZIV+JwY=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=Pqv6Cq+M6VQVzC1+XmDB1WSosV5qU1/civ+sgonxY+Wczhh+QBgoZNFAzEPftTts5 7vrMLc8SmxFbc6efepEUy3Xzo0m0+KDtmldweesVbM2H/8FbO7Xbn54hC0xiayO45X E6JvSs8mvANfPIr8CDwXtRzv8nAn705JhWvxjltTU27/uWWfSvsHzwB11/oDG24BAB fFYE65U43PAY9FE5a3U/uBGwoKBYDbtCrf5mGZR8sZ/EAFtPeJ9Ptu1RqS5iLCh5vc CRZ3YlXPJVCIAuvq6DCuwbrDJPPlDrSPuIDvpCk3ZkvL4x8ZbUcZ3oYVqlQ2pt/8Cd EsDUbewbcsshw== Received: from thinkos.internal.efficios.com (mtl.efficios.com [216.120.195.104]) by smtpout.efficios.com (Postfix) with ESMTPSA id 4jVkHm5VfzzSSp; Thu, 19 Nov 2026 11:21:40 -0500 (EST) From: Mathieu Desnoyers To: Cc: linux-kernel@vger.kernel.org, Mathieu Desnoyers , Juri Lelli , stable@vger.kernel.org Subject: [PATCH v4 07/17] sched/deadline: Do not lose a throttled task switched out and back Date: Thu, 19 Nov 2026 11:21:28 -0500 Message-Id: X-Mailer: git-send-email 2.39.5 In-Reply-To: References: X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Transfer-Encoding: 8bit A SCHED_DEADLINE task can be throttled, switched to another policy, and switched back before its 0-lag time. It may then never run again, not even to die of a fatal signal. A task that leaves SCHED_DEADLINE keeps its parameters until its 0-lag time, so that leaving and coming back gains nothing. Commit 209a0cbda7a0 ("sched/deadline: Improve the tracking of active utilization") moved their reset from the replenishment timer to the inactive timer, which switched_to_dl() cancels. This misses a task that was throttled when it left. An overrun can put its 0-lag time after its replenishment timer. That timer fires while the task is out of the class, and does nothing. On the return of the task, enqueue_dl_entity() leaves it to that timer, which has fired. The task is then on no dl_rq, with no timer pending, until it leaves SCHED_DEADLINE again. Fix this by replenishing the task when the timer finds it out of the class, as for a throttled task that is not queued. Its return then enqueues it. Clearing dl_throttled alone would not do. It would forgive the overrun. A yield left set, or the old deadline of a constrained task, would throttle the task again. The Sashiko AI review of this series found this in the first version of this patch. A cgroup selftest under development hung on this bug about once in 1350 runs. The throttled_round_trip case of deadline_switch_test, added later in this series, fails 8 times out of 8 on v7.3 and v7.4-rc2. It passes with this patch. Fixes: 209a0cbda7a0 ("sched/deadline: Improve the tracking of active utilization") Signed-off-by: Mathieu Desnoyers Acked-by: Juri Lelli Cc: stable@vger.kernel.org --- kernel/sched/deadline.c | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c index b614d5fc1a1a..e4d7cbf4861d 100644 --- a/kernel/sched/deadline.c +++ b/kernel/sched/deadline.c @@ -1233,9 +1233,18 @@ static enum hrtimer_restart dl_task_timer(struct hrtimer *timer) /* * The task might have changed its scheduling policy to something * different than SCHED_DEADLINE (through switched_from_dl()). + * It keeps its parameters until its 0-lag time. If it comes back + * before then, nothing else would lift its throttle. So replenish + * it now, as the !queued case below does. Its return enqueues it. */ - if (!dl_task(p)) + if (!dl_task(p)) { + if (dl_se->dl_throttled && !is_dl_boosted(dl_se)) { + sched_clock_tick(); + update_rq_clock(rq); + replenish_dl_entity(dl_se); + } goto unlock; + } /* * The task might have been boosted by someone else and might be in the -- 2.47.3