linux-kernel - Re: [PATCH 0/3] clocksource/drivers: Prevent clockevent driver unbind

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]

Message-ID: <a728c035-d37c-4e75-89ba-b8081241314f@linaro.org>
Date: Wed, 12 Nov 2025 10:48:22 +0100
From: Daniel Lezcano <daniel.lezcano@...aro.org>
To: Johan Hovold <johan@...nel.org>, Mark Rutland <mark.rutland@....com>,
 Marc Zyngier <maz@...nel.org>, Thomas Gleixner <tglx@...utronix.de>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] clocksource/drivers: Prevent clockevent driver unbind


Hi Johan,

On 11/11/25 16:32, Johan Hovold wrote:
> Clockevents cannot be deregistered so suppress driver bind attributes to
> prevent drivers from being unbound and, for example, releasing
> underlying resources after registration.

For non architected timers, we want to be able to convert the timers as 
modules.

That's an on-going work [1].

Your series assumes we won't convert that into modules, so you do the 
conversion to builtin. But actually, there is a slow move to module 
conversion.

However, given a clockevent can not be unregistered, the 
'suppress_bind_attrs' flag makes sense for those registering one.

   -- Daniel


[1] 
https://lore.kernel.org/all/20250602151853.1942521-1-daniel.lezcano@linaro.org/

-- 
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog