linux-kernel - Re: [PATCH] clocksource: don't run watchdog forever

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: <87zgyr5umc.fsf@nanos.tec.linutronix.de>
Date:   Thu, 25 Mar 2021 12:40:43 +0100
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Feng Tang <feng.tang@...el.com>
Cc:     Peter Zijlstra <peterz@...radead.org>,
        John Stultz <john.stultz@...aro.org>,
        Stephen Boyd <sboyd@...nel.org>, linux-kernel@...r.kernel.org,
        Qais Yousef <qais.yousef@....com>, andi.kleen@...el.com
Subject: Re: [PATCH] clocksource: don't run watchdog forever

On Thu, Mar 25 2021 at 16:34, Feng Tang wrote:
> On Wed, Mar 03, 2021 at 04:50:31PM +0100, Thomas Gleixner wrote:
>
> I've checked one open-sourced BIOS code project: EDK2 (https://github.com/tianocore/edk2),
> where I did some grep and can't find places writting to tsc_adjust msr,
> which can give us more confidence that fewer and fewer BIOS will wrongly
> write to tsc_adjust msr :)

The problem is not EDK2. The problem is in the $VENDOR value add which
is _not_ part of EDK2.

So looking at that code does not make me more confident at all.

Thanks,

        tglx