On Wed, Apr 06, 2022 at 09:29:02PM +0100, Peter Maydell wrote:
> On Wed, 6 Apr 2022 at 19:59, Dr. David Alan Gilbert
> wrote:
> >
> > * Igor Mammedov (imamm...@redhat.com) wrote:
> > > From: "Dr. David Alan Gilbert"
> > >
> > > vmstate_acpi_pcihp_use_acpi_index() was expecting AcpiPciHpState
> >
On Wed, 6 Apr 2022 at 19:59, Dr. David Alan Gilbert wrote:
>
> * Igor Mammedov (imamm...@redhat.com) wrote:
> > From: "Dr. David Alan Gilbert"
> >
> > vmstate_acpi_pcihp_use_acpi_index() was expecting AcpiPciHpState
> > as state but it actually received PIIX4PMState, because
> > VMSTATE_PCI_HOTPL
* Igor Mammedov (imamm...@redhat.com) wrote:
> From: "Dr. David Alan Gilbert"
>
> vmstate_acpi_pcihp_use_acpi_index() was expecting AcpiPciHpState
> as state but it actually received PIIX4PMState, because
> VMSTATE_PCI_HOTPLUG is a macro and not another struct.
> So it ended up accessing random p
From: "Dr. David Alan Gilbert"
vmstate_acpi_pcihp_use_acpi_index() was expecting AcpiPciHpState
as state but it actually received PIIX4PMState, because
VMSTATE_PCI_HOTPLUG is a macro and not another struct.
So it ended up accessing random pointer, which resulted
in 'false' return value and acpi_i
