Re: [Linaro-acpi] [PATCH v3 1/5] ACPI: add in a bad_madt_entry() function to eventually replace the macro

2015-09-10 Thread Al Stone
On 09/10/2015 06:14 AM, Graeme Gregory wrote: > On Wed, Sep 09, 2015 at 03:09:47PM -0600, Al Stone wrote: >> The existing BAD_MADT_ENTRY macro only checks that the size of the data >> structure for an MADT subtable matches the length entry in the subtable. >> This is, unfortunately, not reliable.

Re: [Linaro-acpi] [PATCH v3 1/5] ACPI: add in a bad_madt_entry() function to eventually replace the macro

2015-09-10 Thread Graeme Gregory
On Wed, Sep 09, 2015 at 03:09:47PM -0600, Al Stone wrote: > The existing BAD_MADT_ENTRY macro only checks that the size of the data > structure for an MADT subtable matches the length entry in the subtable. > This is, unfortunately, not reliable. Nor, as it turns out, does it have > anything to

Re: [Linaro-acpi] [PATCH v3 1/5] ACPI: add in a bad_madt_entry() function to eventually replace the macro

2015-09-10 Thread Graeme Gregory
On Wed, Sep 09, 2015 at 03:09:47PM -0600, Al Stone wrote: > The existing BAD_MADT_ENTRY macro only checks that the size of the data > structure for an MADT subtable matches the length entry in the subtable. > This is, unfortunately, not reliable. Nor, as it turns out, does it have > anything to

Re: [Linaro-acpi] [PATCH v3 1/5] ACPI: add in a bad_madt_entry() function to eventually replace the macro

2015-09-10 Thread Al Stone
On 09/10/2015 06:14 AM, Graeme Gregory wrote: > On Wed, Sep 09, 2015 at 03:09:47PM -0600, Al Stone wrote: >> The existing BAD_MADT_ENTRY macro only checks that the size of the data >> structure for an MADT subtable matches the length entry in the subtable. >> This is, unfortunately, not reliable.