[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230921171408.GA26395@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
Date: Thu, 21 Sep 2023 10:14:08 -0700
From: Saurabh Singh Sengar <ssengar@...ux.microsoft.com>
To: Mathias Krause <minipli@...ecurity.net>
Cc: kys@...rosoft.com, haiyangz@...rosoft.com, wei.liu@...nel.org,
decui@...rosoft.com, tglx@...utronix.de, mingo@...hat.com,
bp@...en8.de, dave.hansen@...ux.intel.com, x86@...nel.org,
hpa@...or.com, linux-hyperv@...r.kernel.org,
linux-kernel@...r.kernel.org, mikelley@...rosoft.com,
ssengar@...rosoft.com
Subject: Re: [PATCH] x86/hyperv: Remove hv_vtl_early_init initcall
On Thu, Sep 21, 2023 at 09:17:24AM +0200, Mathias Krause wrote:
> On 20.09.23 06:52, Saurabh Sengar wrote:
> > There has been cases reported where HYPERV_VTL_MODE is enabled by mistake,
> > on a non Hyper-V platforms. This causes the hv_vtl_early_init function to
> > be called in an non Hyper-V/VTL platforms which results the memory
> > corruption.
> >
> > Remove the early_initcall for vhv_vtl_early_init and call it at the end of
vhv_vtl_early_init need to be replaced with hv_vtl_early_init here.
Wei,
Do you need a V2 for it ?
- Saurabh
Powered by blists - more mailing lists