Re: [PATCH v3 0/5] ACPI: Provide better MADT subtable sanity checks

2015-09-16 Thread Rafael J. Wysocki
On Wednesday, September 16, 2015 10:27:57 AM Al Stone wrote: > On 09/16/2015 10:24 AM, Al Stone wrote: > > On 09/15/2015 08:44 PM, Rafael J. Wysocki wrote: > >> On Tuesday, September 15, 2015 03:13:12 PM Al Stone wrote: > >>> On 09/09/2015 03:09 PM, Al Stone wrote: > Currently, the

Re: [PATCH v3 0/5] ACPI: Provide better MADT subtable sanity checks

2015-09-16 Thread Al Stone
On 09/16/2015 10:27 AM, Al Stone wrote: > On 09/16/2015 10:24 AM, Al Stone wrote: >> On 09/15/2015 08:44 PM, Rafael J. Wysocki wrote: >>> On Tuesday, September 15, 2015 03:13:12 PM Al Stone wrote: On 09/09/2015 03:09 PM, Al Stone wrote: > Currently, the BAD_MADT_ENTRY macro is used to do

Re: [PATCH v3 0/5] ACPI: Provide better MADT subtable sanity checks

2015-09-16 Thread Al Stone
On 09/16/2015 10:24 AM, Al Stone wrote: > On 09/15/2015 08:44 PM, Rafael J. Wysocki wrote: >> On Tuesday, September 15, 2015 03:13:12 PM Al Stone wrote: >>> On 09/09/2015 03:09 PM, Al Stone wrote: Currently, the BAD_MADT_ENTRY macro is used to do a very simple sanity check on the various

Re: [PATCH v3 0/5] ACPI: Provide better MADT subtable sanity checks

2015-09-16 Thread Al Stone
On 09/15/2015 08:44 PM, Rafael J. Wysocki wrote: > On Tuesday, September 15, 2015 03:13:12 PM Al Stone wrote: >> On 09/09/2015 03:09 PM, Al Stone wrote: >>> Currently, the BAD_MADT_ENTRY macro is used to do a very simple sanity >>> check on the various subtables that are defined for the MADT. The

Re: [PATCH v3 0/5] ACPI: Provide better MADT subtable sanity checks

2015-09-16 Thread Al Stone
On 09/15/2015 08:44 PM, Rafael J. Wysocki wrote: > On Tuesday, September 15, 2015 03:13:12 PM Al Stone wrote: >> On 09/09/2015 03:09 PM, Al Stone wrote: >>> Currently, the BAD_MADT_ENTRY macro is used to do a very simple sanity >>> check on the various subtables that are defined for the MADT. The

Re: [PATCH v3 0/5] ACPI: Provide better MADT subtable sanity checks

2015-09-16 Thread Al Stone
On 09/16/2015 10:24 AM, Al Stone wrote: > On 09/15/2015 08:44 PM, Rafael J. Wysocki wrote: >> On Tuesday, September 15, 2015 03:13:12 PM Al Stone wrote: >>> On 09/09/2015 03:09 PM, Al Stone wrote: Currently, the BAD_MADT_ENTRY macro is used to do a very simple sanity check on the various

Re: [PATCH v3 0/5] ACPI: Provide better MADT subtable sanity checks

2015-09-16 Thread Al Stone
On 09/16/2015 10:27 AM, Al Stone wrote: > On 09/16/2015 10:24 AM, Al Stone wrote: >> On 09/15/2015 08:44 PM, Rafael J. Wysocki wrote: >>> On Tuesday, September 15, 2015 03:13:12 PM Al Stone wrote: On 09/09/2015 03:09 PM, Al Stone wrote: > Currently, the BAD_MADT_ENTRY macro is used to do

Re: [PATCH v3 0/5] ACPI: Provide better MADT subtable sanity checks

2015-09-16 Thread Rafael J. Wysocki
On Wednesday, September 16, 2015 10:27:57 AM Al Stone wrote: > On 09/16/2015 10:24 AM, Al Stone wrote: > > On 09/15/2015 08:44 PM, Rafael J. Wysocki wrote: > >> On Tuesday, September 15, 2015 03:13:12 PM Al Stone wrote: > >>> On 09/09/2015 03:09 PM, Al Stone wrote: > Currently, the

Re: [PATCH v3 0/5] ACPI: Provide better MADT subtable sanity checks

2015-09-15 Thread Rafael J. Wysocki
On Tuesday, September 15, 2015 03:13:12 PM Al Stone wrote: > On 09/09/2015 03:09 PM, Al Stone wrote: > > Currently, the BAD_MADT_ENTRY macro is used to do a very simple sanity > > check on the various subtables that are defined for the MADT. The check > > compares the size of the subtable data

Re: [PATCH v3 0/5] ACPI: Provide better MADT subtable sanity checks

2015-09-15 Thread Al Stone
On 09/09/2015 03:09 PM, Al Stone wrote: > Currently, the BAD_MADT_ENTRY macro is used to do a very simple sanity > check on the various subtables that are defined for the MADT. The check > compares the size of the subtable data structure as defined by ACPICA to > the length entry in the subtable.

Re: [PATCH v3 0/5] ACPI: Provide better MADT subtable sanity checks

2015-09-15 Thread Rafael J. Wysocki
On Tuesday, September 15, 2015 03:13:12 PM Al Stone wrote: > On 09/09/2015 03:09 PM, Al Stone wrote: > > Currently, the BAD_MADT_ENTRY macro is used to do a very simple sanity > > check on the various subtables that are defined for the MADT. The check > > compares the size of the subtable data

Re: [PATCH v3 0/5] ACPI: Provide better MADT subtable sanity checks

2015-09-15 Thread Al Stone
On 09/09/2015 03:09 PM, Al Stone wrote: > Currently, the BAD_MADT_ENTRY macro is used to do a very simple sanity > check on the various subtables that are defined for the MADT. The check > compares the size of the subtable data structure as defined by ACPICA to > the length entry in the subtable.

Re: [Linaro-acpi] [PATCH v3 0/5] ACPI: Provide better MADT subtable sanity checks

2015-09-10 Thread Graeme Gregory
On Wed, Sep 09, 2015 at 03:09:46PM -0600, Al Stone wrote: > Currently, the BAD_MADT_ENTRY macro is used to do a very simple sanity > check on the various subtables that are defined for the MADT. The check > compares the size of the subtable data structure as defined by ACPICA to > the length

Re: [Linaro-acpi] [PATCH v3 0/5] ACPI: Provide better MADT subtable sanity checks

2015-09-10 Thread Graeme Gregory
On Wed, Sep 09, 2015 at 03:09:46PM -0600, Al Stone wrote: > Currently, the BAD_MADT_ENTRY macro is used to do a very simple sanity > check on the various subtables that are defined for the MADT. The check > compares the size of the subtable data structure as defined by ACPICA to > the length

[PATCH v3 0/5] ACPI: Provide better MADT subtable sanity checks

2015-09-09 Thread Al Stone
Currently, the BAD_MADT_ENTRY macro is used to do a very simple sanity check on the various subtables that are defined for the MADT. The check compares the size of the subtable data structure as defined by ACPICA to the length entry in the subtable. If they are not the same, the assumption is

[PATCH v3 0/5] ACPI: Provide better MADT subtable sanity checks

2015-09-09 Thread Al Stone
Currently, the BAD_MADT_ENTRY macro is used to do a very simple sanity check on the various subtables that are defined for the MADT. The check compares the size of the subtable data structure as defined by ACPICA to the length entry in the subtable. If they are not the same, the assumption is