linux-kernel - RE: 0xB16B00B5? Really? (was Re: Move hyperv out of the drivers/staging/ directory)

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]

Date:	Fri, 20 Jul 2012 14:00:56 +0000
From:	KY Srinivasan <kys@...rosoft.com>
To:	Bjørn Mork <bjorn@...k.no>
CC:	"Greg KH (gregkh@...uxfoundation.org)" <gregkh@...uxfoundation.org>,
	Paolo Bonzini <pbonzini@...hat.com>,
	"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"virtualization@...ts.osdl.org" <virtualization@...ts.osdl.org>
Subject: RE: 0xB16B00B5? Really? (was Re: Move hyperv out of the
 drivers/staging/ directory)



> -----Original Message-----
> From: Bjørn Mork [mailto:bjorn@...k.no]
> Sent: Friday, July 20, 2012 3:59 AM
> To: KY Srinivasan
> Cc: Greg KH (gregkh@...uxfoundation.org); Paolo Bonzini;
> devel@...uxdriverproject.org; linux-kernel@...r.kernel.org;
> virtualization@...ts.osdl.org
> Subject: Re: 0xB16B00B5? Really? (was Re: Move hyperv out of the
> drivers/staging/ directory)
> 
> KY Srinivasan <kys@...rosoft.com> writes:
> 
> > Here is the link that describes how the guest ID should be composed:
> >
> > http://msdn.microsoft.com/en-
> us/library/windows/hardware/ff542653%28v=vs.85%29.aspx
> 
> The unwanted value does not conform to those rules:  Linux is not yet at
> major version 0xB5.
> 
> I propose that you change this into a macro actually taking the OS
> major/minor version into account, keeping the 0xB16B vendor ID (which
> seems safest as the vendor ID registration process seems a bit unclear)

Thank you for your interest in fixing this problem. When we decide to change this
ID, we will conform to the MSFT guidelines on constructing this guest ID.

Regards,

K. Y