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: <aRRouCZKoPYKH5fA@hovoldconsulting.com>
Date: Wed, 12 Nov 2025 12:00:08 +0100
From: Johan Hovold <johan@...nel.org>
To: Daniel Lezcano <daniel.lezcano@...aro.org>
Cc: Mark Rutland <mark.rutland@....com>, Marc Zyngier <maz@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] clocksource/drivers: Prevent clockevent driver unbind

On Wed, Nov 12, 2025 at 10:48:22AM +0100, Daniel Lezcano wrote:

> 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.

No, that's not the case. The builtin_platform_driver macro still allows
building drivers as modules, it just prevents unloading them.

Johan