linux-kernel - Re: [PATCH] clocksource: Update registration failure behavior documentation

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] [day] [month] [year] [list]

Message-ID: <87v7g38lzm.ffs@tglx>
Date: Wed, 11 Feb 2026 14:10:05 +0100
From: Thomas Gleixner <tglx@...nel.org>
To: Zhan Xusheng <zhanxusheng1024@...il.com>
Cc: linux-kernel@...r.kernel.org, Zhan Xusheng <zhanxusheng@...omi.com>
Subject: Re: [PATCH] clocksource: Update registration failure behavior
 documentation

On Tue, Feb 10 2026 at 10:56, Zhan Xusheng wrote:
> The documentation for clocksource registration functions has been updated
> to clarify the failure behavior. Specifically, the return value on failure
> is no longer an error code (-EBUSY). Instead, the function will issue
> warnings but always return 0 on failure, as previously successful
> registration attempts might still leave the system in an inconsistent
> state.

This changelog is completely made up. Which failure is ignored there and
whats the inconsistent state of a previous attempt?

The -EBUSY comment is a leftover from the original implementation. and
the pr_warn() about the vdso clock mode is harmless as it still leaves
the system in a consistent state. Just the VDSO functionality is not
enabled.

This AI slop starts to become annoying.

Thanks,

        tglx