linux-kernel - Re: [PATCH v2] clocksource: Defer marking clocksources unstable to kthread

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: <87ecz62nn4.ffs@tglx>
Date: Sun, 09 Mar 2025 17:07:43 +0100
From: Thomas Gleixner <tglx@...utronix.de>
To: Yafang Shao <laoar.shao@...il.com>
Cc: paulmck@...nel.org, linux-kernel@...r.kernel.org, jstultz@...gle.com,
 sboyd@...nel.org, christian@...sel.eu, kernel-team@...a.com, Peter
 Zijlstra <peterz@...radead.org>, Michal Koutný
 <mkoutny@...e.com>, Vincent
 Guittot <vincent.guittot@...aro.org>
Subject: Re: [PATCH v2] clocksource: Defer marking clocksources unstable to
 kthread

On Sun, Mar 09 2025 at 19:36, Yafang Shao wrote:
> On Sun, Mar 9, 2025 at 12:38 AM Thomas Gleixner <tglx@...utronix.de> wrote:
>> So as this got introduced in the 6.14 merge window, the proper fix is to
>> revert commit 8722903cbb8f and send it back to the drawing board. It was
>> clearly never tested with the various possibilities which invoke
>> mark_tsc*_unstable().
>
> Hello Thomas,
>
> It has been reverted by the following commit
> b9f2b29b9494 ("sched: Don't define sched_clock_irqtime as static key")

That does not help much because the commit is in the sched/core branch,
which is scheduled for the next merge window. But this wants to be fixed
in Linus tree before 6.14 final. Peter?

Thanks,

        tglx