linux-kernel - Re: [PATCH 1/1] Drivers: hv: vmbus: Add VMbus IMC device to unsupported list

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

Date:   Mon, 25 Apr 2022 15:31:57 +0000
From:   Wei Liu <wei.liu@...nel.org>
To:     Michael Kelley <mikelley@...rosoft.com>
Cc:     kys@...rosoft.com, haiyangz@...rosoft.com, sthemmin@...rosoft.com,
        wei.liu@...nel.org, linux-kernel@...r.kernel.org,
        linux-hyperv@...r.kernel.org, vkuznets@...hat.com,
        decui@...rosoft.com
Subject: Re: [PATCH 1/1] Drivers: hv: vmbus: Add VMbus IMC device to
 unsupported list

On Tue, Apr 12, 2022 at 07:49:00PM -0700, Michael Kelley wrote:
> Hyper-V may offer an Initial Machine Configuration (IMC) synthetic
> device to guest VMs. The device may be used by Windows guests to get
> specialization information, such as the hostname.  But the device
> is not used in Linux and there is no Linux driver, so it is
> unsupported.
> 
> Currently, the IMC device GUID is not recognized by the VMbus driver,
> which results in an "Unknown GUID" error message during boot. Add
> the GUID to the list of known but unsupported devices so that the
> error message is not generated. Other than avoiding the error message,
> there is no change in guest behavior.
> 
> Signed-off-by: Michael Kelley <mikelley@...rosoft.com>

Applied to hyperv-next. Thanks.