linux-kernel - Re: [PATCH 3.12 81/88] KVM: x86: expose invariant tsc cpuid bit (v2)

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <62f0306d-a4ff-ac6d-9806-7c6a6500ffa4@suse.cz>
Date:	Thu, 14 Jul 2016 11:22:45 +0200
From:	Jiri Slaby <jslaby@...e.cz>
To:	Paolo Bonzini <pbonzini@...hat.com>, stable@...r.kernel.org
Cc:	linux-kernel@...r.kernel.org, Marcelo Tosatti <mtosatti@...hat.com>
Subject: Re: [PATCH 3.12 81/88] KVM: x86: expose invariant tsc cpuid bit (v2)

On 07/14/2016, 10:40 AM, Paolo Bonzini wrote:
> 
> 
> On 14/07/2016 10:16, Jiri Slaby wrote:
>> From: Marcelo Tosatti <mtosatti@...hat.com>
>>
>> 3.12-stable review patch.  If anyone has any objections, please let me know.
> 
> Why stable?  The commit is in 3.16, but AFAICS it never went into other
> stable kernels.

Hi,

we (SUSE) have the patch in SLE12 (based on 3.12) for some time as our
customer needs to see the invtsc flag. And given it is so simple and
belongs IMO to the "New device IDs and quirks are also accepted."
category, I decided to take it into 3.12.

If you see some problem this could lead to, I can drop it from stable of
course. But then I would be definitely interested in details to fix this
in SLE12 as well.

thanks,
-- 
js
suse labs