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: <20170210143946.GA10648@kroah.com>
Date:   Fri, 10 Feb 2017 15:39:46 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     KY Srinivasan <kys@...rosoft.com>
Cc:     "olaf@...fle.de" <olaf@...fle.de>,
        "jasowang@...hat.com" <jasowang@...hat.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "apw@...onical.com" <apw@...onical.com>,
        "devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
        "leann.ogasawara@...onical.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 04:24:40PM +0000, KY Srinivasan wrote:
> 
> 
> > -----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.

Next time please put that in the patch area.

thanks,

greg k-h