linux-kernel - RE: [PATCH 2/3 v6] ACPI: allow longer device IDs

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: <PH0PR21MB30251D429344378FE8D47E35D7199@PH0PR21MB3025.namprd21.prod.outlook.com>
Date:   Thu, 24 Mar 2022 19:24:33 +0000
From:   "Michael Kelley (LINUX)" <mikelley@...rosoft.com>
To:     Ard Biesheuvel <ardb@...nel.org>
CC:     jason <jason@...c4.com>,
        Andy Shevchenko <andy.shevchenko@...il.com>,
        "Rafael J. Wysocki" <rafael@...nel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        linux-crypto <linux-crypto@...r.kernel.org>,
        ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
        Alexander Graf <graf@...zon.com>,
        Mika Westerberg <mika.westerberg@...ux.intel.com>,
        Hans de Goede <hdegoede@...hat.com>,
        Len Brown <lenb@...nel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: RE: [PATCH 2/3 v6] ACPI: allow longer device IDs

From: Ard Biesheuvel <ardb@...nel.org> Sent: Tuesday, March 22, 2022 3:07 PM
> 
> On Tue, 22 Mar 2022 at 20:59, Michael Kelley (LINUX)
> <mikelley@...rosoft.com> wrote:
> >
> > The Hyper-V guys pass along their thanks for your suggestion.  They have
> > created an internal build with the change and verified that it preserves
> > compatibility with Windows guests.  I've tested with Linux guests and
> > Jason's new driver (modified to look for "VMGENCTR"), and it all looks good.
> > It will take a little while to wend its way through the Windows/Hyper-V
> > release system, but they are planning to take the change.
> >
> 
> Thanks for reporting back.
> 
> Will the spec be updated accordingly?

The Hyper-V team is looking into updating the spec.  The document
is 10 years old, so they need to find the original source for the PDF.

Michael