linux-kernel - RE: [PATCH 1/1] Drivers: hv: Fix the bug in generating the guest ID

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: <DM5PR03MB24904281A672B748AAF203B5A04E0@DM5PR03MB2490.namprd03.prod.outlook.com>
Date:   Sat, 4 Feb 2017 16:24:40 +0000
From:   KY Srinivasan <kys@...rosoft.com>
To:     Greg KH <gregkh@...uxfoundation.org>
CC:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
        "olaf@...fle.de" <olaf@...fle.de>,
        "apw@...onical.com" <apw@...onical.com>,
        "vkuznets@...hat.com" <vkuznets@...hat.com>,
        "jasowang@...hat.com" <jasowang@...hat.com>,
        "leann.ogasawara@...onical.com" <leann.ogasawara@...onical.com>
Subject: RE: [PATCH 1/1] Drivers: hv: Fix the bug in generating the guest ID



> -----Original Message-----
> From: Greg KH [mailto:gregkh@...uxfoundation.org]
> Sent: Saturday, February 4, 2017 7:58 AM
> To: KY Srinivasan <kys@...rosoft.com>
> Cc: linux-kernel@...r.kernel.org; devel@...uxdriverproject.org;
> olaf@...fle.de; apw@...onical.com; vkuznets@...hat.com;
> jasowang@...hat.com; leann.ogasawara@...onical.com
> Subject: Re: [PATCH 1/1] Drivers: hv: Fix the bug in generating the guest ID
> 
> On Sat, Feb 04, 2017 at 08:46:23AM -0700, kys@...hange.microsoft.com
> wrote:
> > From: K. Y. Srinivasan <kys@...rosoft.com>
> >
> > Fix the bug in the generation of the guest ID. Without this fix
> > the host side telemetry code is broken.
> >
> > Signed-off-by: K. Y. Srinivasan <kys@...rosoft.com>
> 
> If it's broken, does that mean this should go to the stable kernels?
> What commit caused the breakage?

Commit 352c9624242d5836ad8a960826183011367871a4 introduced the bug.
The stable kernels are fine.

Thanks,

K. Y
> 
> thanks,
> 
> greg k-h