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  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:   Thu, 21 May 2020 03:53:18 +0300
From:   Serge Semin <>
To:     Thomas Gleixner <>,
        Thomas Bogendoerfer <>,
        Daniel Lezcano <>,
        Jamie Iles <>,
        Rob Herring <>,
        Dinh Nguyen <>,
        Heiko Stuebner <>, Arnd Bergmann <>
CC:     Serge Semin <>,
        Serge Semin <>,
        Alexey Malahov <>,
        Paul Burton <>,
        Ralf Baechle <>,
        Alessandro Zummo <>,
        Alexandre Belloni <>,
        Rob Herring <>, <>,
        <>, <>,
        Allison Randal <>,
        Greg Kroah-Hartman <>,
        Alexios Zavras <>,
Subject: [PATCH v4 5/7] clocksource: dw_apb_timer_of: Fix missing clockevent timers

Commit 100214889973 ("clocksource: dw_apb_timer_of: use
clocksource_of_init") replaced a publicly available driver
initialization method with one called by the timer_probe() method
available after CLKSRC_OF. In current implementation it traverses
all the timers available in the system and calls their initialization
methods if corresponding devices were either in dtb or in acpi. But
if before the commit any number of available timers would be installed
as clockevent and clocksource devices, after that there would be at most
two. The rest are just ignored since default case branch doesn't do
anything. I don't see a reason of such behaviour, neither the commit
message explains it. Moreover this might be wrong if on some platforms
these timers might be used for different purpose, as virtually CPU-local
clockevent timers and as an independent broadcast timer. So in order
to keep the compatibility with the platforms where the order of the
timers detection has some meaning, lets add the secondly discovered
timer to be of clocksource/sched_clock type, while the very first and
the others would provide the clockevents service.

Fixes: 100214889973 ("clocksource: dw_apb_timer_of: use clocksource_of_init")
Signed-off-by: Serge Semin <>
Cc: Alexey Malahov <>
Cc: Thomas Bogendoerfer <>
Cc: Paul Burton <>
Cc: Ralf Baechle <>
Cc: Alessandro Zummo <>
Cc: Alexandre Belloni <>
Cc: Arnd Bergmann <>
Cc: Rob Herring <>
 drivers/clocksource/dw_apb_timer_of.c | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/drivers/clocksource/dw_apb_timer_of.c b/drivers/clocksource/dw_apb_timer_of.c
index 0a2505b323d7..0b61b90a525e 100644
--- a/drivers/clocksource/dw_apb_timer_of.c
+++ b/drivers/clocksource/dw_apb_timer_of.c
@@ -146,10 +146,6 @@ static int num_called;
 static int __init dw_apb_timer_init(struct device_node *timer)
 	switch (num_called) {
-	case 0:
-		pr_debug("%s: found clockevent timer\n", __func__);
-		add_clockevent(timer);
-		break;
 	case 1:
 		pr_debug("%s: found clocksource timer\n", __func__);
@@ -160,6 +156,8 @@ static int __init dw_apb_timer_init(struct device_node *timer)
+		pr_debug("%s: found clockevent timer\n", __func__);
+		add_clockevent(timer);

Powered by blists - more mailing lists