linux-kernel - RE: [v3] x86/tsc: Unset TSC_KNOWN_FREQ and TSC

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

Message-ID: <a764bca368794eccbda39238d85da9ba@svr-orw-mbx-01.mgc.mentorg.com>
Date:   Wed, 22 Jan 2020 04:24:42 +0000
From:   "Kumar, Vipul" <Vipul_Kumar@...tor.com>
To:     Sasha Levin <sashal@...nel.org>,
        Vipul Kumar <vipulk0511@...il.com>,
        Daniel Lezcano <daniel.lezcano@...aro.org>
CC:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Stable <stable@...r.kernel.org>,
        "stable@...r.kernel.org" <stable@...r.kernel.org>,
        "stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: RE: [v3] x86/tsc: Unset TSC_KNOWN_FREQ and TSC_RELIABLE flags on
 Intel Bay Trail SoC

Hi Sasha,

As this patch is based on commit f3a02ecebed7 ("x86/tsc: Set TSC_KNOWN_FREQ and TSC_RELIABLE flags on Intel Atom SoCs") which was introduced in 4.14.

So, this patch is not applicable for kernel versions prior to 4.14.

As this patch is under review, can we put it on hold ?

Regards,
Vipul 

-----Original Message-----
From: Sasha Levin [mailto:sashal@...nel.org] 
Sent: 22 January 2020 07:56
To: Sasha Levin <sashal@...nel.org>; Vipul Kumar <vipulk0511@...il.com>; Kumar, Vipul <Vipul_Kumar@...tor.com>; Daniel Lezcano <daniel.lezcano@...aro.org>
Cc: linux-kernel@...r.kernel.org; Stable <stable@...r.kernel.org>; stable@...r.kernel.org; stable@...r.kernel.org
Subject: Re: [v3] x86/tsc: Unset TSC_KNOWN_FREQ and TSC_RELIABLE flags on Intel Bay Trail SoC

Hi,

[This is an automated email]

This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all

The bot has tested the following trees: v5.4.13, v4.19.97, v4.14.166, v4.9.210, v4.4.210.

v5.4.13: Build OK!
v4.19.97: Build OK!
v4.14.166: Build failed! Errors:

v4.9.210: Failed to apply! Possible dependencies:
    f3a02ecebed7 ("x86/tsc: Set TSC_KNOWN_FREQ and TSC_RELIABLE flags on Intel Atom SoCs")

v4.4.210: Failed to apply! Possible dependencies:
    0007bccc3cfd ("x86: Replace RDRAND forced-reseed with simple sanity check")
    07dc900e17a9 ("perf/x86: Move Kconfig.perf and other perf configuration bits to events/Kconfig")
    1b74dde7c47c ("x86/cpu: Convert printk(KERN_<LEVEL> ...) to pr_<level>(...)")
    218cfe4ed888 ("perf/x86: Move perf_event_amd_ibs.c ....... => x86/events/amd/ibs.c")
    39b0332a2158 ("perf/x86: Move perf_event_amd.c ........... => x86/events/amd/core.c")
    442f5c74cbea ("perf/x86: Use INST_RETIRED.TOTAL_CYCLES_PS for cycles:pp for Skylake")
    5b26547dd7fa ("perf/x86: Move perf_event_amd_iommu.[ch] .. => x86/events/amd/iommu.[ch]")
    724697648eec ("perf/x86: Use INST_RETIRED.PREC_DIST for cycles: ppp")
    e633c65a1d58 ("x86/perf/intel/uncore: Make the Intel uncore PMU driver modular")
    fa9cbf320e99 ("perf/x86: Move perf_event.c ............... => x86/events/core.c")


NOTE: The patch will not be queued to stable trees until it is upstream.

How should we proceed with this patch?

-- 
Thanks,
Sasha