linux-kernel - Re: [LKP] [PATCH] x86: fix rdmsr MSR_PLATFORM

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

Message-ID: <CANRm+CzXjODDjiSHeyHHeaAyLjrBBJ9QzmCtFsyxJc=Qe4KMZg@mail.gmail.com>
Date:	Thu, 23 Jun 2016 16:00:09 +0800
From:	Wanpeng Li <kernellwp@...il.com>
To:	Yu Chen <yu.chen.surf@...il.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Radim Krčmář <rkrcmar@...hat.com>,
	kvm <kvm@...r.kernel.org>,
	Linux PM list <linux-pm@...r.kernel.org>,
	"the arch/x86 maintainers" <x86@...nel.org>,
	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-acpi@...r.kernel.org, Ingo Molnar <mingo@...hat.com>,
	Jacob Pan <jacob.jun.pan@...el.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	Paolo Bonzini <pbonzini@...hat.com>,
	Zhang Rui <rui.zhang@...el.com>, lkp@...org,
	Wanpeng Li <wanpeng.li@...mail.com>
Subject: Re: [LKP] [PATCH] x86: fix rdmsr MSR_PLATFORM_INFO unsafe warning in
 kvm guest

2016-06-23 15:41 GMT+08:00 Wanpeng Li <kernellwp@...il.com>:
> Hi Yu，
> 2016-06-23 15:37 GMT+08:00 Yu Chen <yu.chen.surf@...il.com>:
>> On Thu, Jun 23, 2016 at 3:09 PM, Thomas Gleixner <tglx@...utronix.de> wrote:
>>> On Wed, 22 Jun 2016, Wanpeng Li wrote:
>>>> After commit (fc141535ad8 : "x86 tsc_msr: Extend to include Intel Core
>>>
>>> Where did you find that commit? It's neither in Linus tree nor in tip.
>>>
>> It is in Len's tree, we are planing to resend the patchset with Wanpeng's fix
>> merged with a credit to him in commit msg, thanks for Wanpeng's effort.
>> thanks all.
>
> I prefer this patch can be applied separately instead of fold into the
> bad commit since it shows the issue when access MSR_PLATFORM_INFO in
> kvm guest and other guys who want to access MSR_PLATFORM_INFO later
> can find the changelog and make better decisions.

Thomas, does it make sense to keep separate?

Regards,
Wanpeng Li