linux-kernel - [PATCH v4.19.y 4/4] kernel/sched: Remove dl

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 22 Aug 2022 13:13:48 +0530
From:   Ankit Jain <ankitja@...are.com>
To:     juri.lelli@...hat.com, bristot@...hat.com, l.stach@...gutronix.de,
        suhui_kernel@....com, msimmons@...hat.com, peterz@...radead.org,
        glenn@...ora.tech, stable@...r.kernel.org,
        linux-kernel@...r.kernel.org, gregkh@...uxfoundation.org
Cc:     srivatsab@...are.com, srivatsa@...il.mit.edu, akaher@...are.com,
        amakhalov@...are.com, vsirnapalli@...are.com,
        sturlapati@...are.com, bordoloih@...are.com, keerthanak@...are.com,
        Ankit Jain <ankitja@...are.com>
Subject: [PATCH v4.19.y 4/4] kernel/sched: Remove dl_boosted flag comment

From: Hui Su <suhui_kernel@....com>

commit 0e3872499de1a1230cef5221607d71aa09264bd5 upstream.

since commit 2279f540ea7d ("sched/deadline: Fix priority
inheritance with multiple scheduling classes"), we should not
keep it here.

Signed-off-by: Hui Su <suhui_kernel@....com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@...radead.org>
Reviewed-by: Daniel Bristot de Oliveira <bristot@...hat.com>
Link: https://lore.kernel.org/r/20220107095254.GA49258@localhost.localdomain
[Ankit: Regenerated the patch for v4.19.y]
Signed-off-by: Ankit Jain <ankitja@...are.com>
---
 include/linux/sched.h | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/include/linux/sched.h b/include/linux/sched.h
index 2ed820558da1..bc04745da6c1 100644
--- a/include/linux/sched.h
+++ b/include/linux/sched.h
@@ -528,10 +528,6 @@ struct sched_dl_entity {
 	 * task has to wait for a replenishment to be performed at the
 	 * next firing of dl_timer.
 	 *
-	 * @dl_boosted tells if we are boosted due to DI. If so we are
-	 * outside bandwidth enforcement mechanism (but only until we
-	 * exit the critical section);
-	 *
 	 * @dl_yielded tells if task gave up the CPU before consuming
 	 * all its available runtime during the last job.
 	 *
-- 
2.34.1