linux-kernel - Re: [PATCH AUTOSEL 5.1 013/219] x86/tsc: Use CPUID.0x16 to calculate missing crystal frequency

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: <20190722003915.GB1607@sasha-vm>
Date:   Sun, 21 Jul 2019 20:39:15 -0400
From:   Sasha Levin <sashal@...nel.org>
To:     Daniel Drake <drake@...lessm.com>
Cc:     Linux Kernel <linux-kernel@...r.kernel.org>,
        stable@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
        Andy Lutomirski <luto@...nel.org>,
        Borislav Petkov <bp@...en8.de>,
        "H . Peter Anvin" <hpa@...or.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Peter Zijlstra <peterz@...radead.org>,
        Len Brown <len.brown@...el.com>,
        Linux Upstreaming Team <linux@...lessm.com>,
        "Wysocki, Rafael J" <rafael.j.wysocki@...el.com>,
        Ingo Molnar <mingo@...nel.org>
Subject: Re: [PATCH AUTOSEL 5.1 013/219] x86/tsc: Use CPUID.0x16 to calculate
 missing crystal frequency

On Tue, Jul 16, 2019 at 10:56:59AM +0800, Daniel Drake wrote:
>Hi,
>
>On Mon, Jul 15, 2019 at 9:38 PM Sasha Levin <sashal@...nel.org> wrote:
>> From: Daniel Drake <drake@...lessm.com>
>>
>> [ Upstream commit 604dc9170f2435d27da5039a3efd757dceadc684 ]
>
>In my opinion this is not stable kernel material.
>
>It alone does not solve a particular bug. It's part of a larger effort
>to decrease usage of the 8254 PIT on modern platforms, which solves a
>real problem (see "x86: skip PIT initialization on modern chipsets"),
>but I'd conservatively recommend just leaving these patches out of the
>stable tree. The problem has existed for a while without a
>particularly wide impact, and there is a somewhat documented
>workaround of changing BIOS settings.

I've dropped it, thanks!

--
Thanks,
Sasha