linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/5] ACPI: add in a bad_madt_entry() function to eventually replace the macro
Date: Fri, 11 Sep 2015 09:49:43 +0100	[thread overview]
Message-ID: <55F295A7.20406@arm.com> (raw)
In-Reply-To: <55F1EB81.9030908@redhat.com>



On 10/09/15 21:43, Al Stone wrote:
> On 09/10/2015 10:20 AM, Sudeep Holla wrote:
>>

[...]

>>
>>  From the code inspection, I can see we have 3 users of acpi_parse_entries not
>> just MADT but also PCC and NUMA/SRAT
>>
>> Something like this solves this issue:
>> -              if (bad_madt_entry(table_header, entry))
>> +              if (!strncmp(id, ACPI_SIG_MADT, 4) &&
>> +                      bad_madt_entry(table_header, entry)
>>
>>
>> Or am I still missing something ?
>
> Nope, I missed it.  Your fix above will solve the problem; I misunderstood
> how acpi_parse_entries() was being used -- somehow I had it in my head that
> only MADT was in use, and just not seeing that it's being used for several
> other subtable traversals also.  Sorry about that, Sudeep.  My mistake.
>

No worries.

> I'll add this fix for a v4, but I'll wait for a few days to see if I get any
> additional comments -- I haven't heard from any x86, ia64 or ACPI maintainers

Makes sense.

> yet.  OTOH, it's nice to know we've already found and fixed two sets of arm64
> ACPI tables that are in error by using these patches, even with the flaws :).
>

Very much true indeed :)

Regards,
Sudeep

  reply	other threads:[~2015-09-11  8:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-19 22:07 [PATCH v2 0/5] ACPI: Provide better MADT subtable sanity checks Al Stone
2015-08-19 22:07 ` [PATCH v2 1/5] ACPI: add in a bad_madt_entry() function to eventually replace the macro Al Stone
2015-08-26 15:38   ` Timur Tabi
2015-08-26 20:30     ` Al Stone
2015-09-07 15:32   ` Sudeep Holla
2015-09-08 23:00     ` Al Stone
2015-09-09 19:57     ` Al Stone
2015-09-10 16:20       ` Sudeep Holla
2015-09-10 20:43         ` Al Stone
2015-09-11  8:49           ` Sudeep Holla [this message]
2015-08-19 22:07 ` [PATCH v2 2/5] ACPI / ARM64: remove usage of BAD_MADT_ENTRY/BAD_MADT_GICC_ENTRY Al Stone
2015-08-20 10:13   ` Will Deacon
2015-08-20 16:57     ` Al Stone
2015-08-24 10:04       ` Will Deacon
2015-08-19 22:07 ` [PATCH v2 3/5] ACPI / IA64: remove usage of BAD_MADT_ENTRY Al Stone
2015-08-19 22:07 ` [PATCH v2 4/5] ACPI / X86: " Al Stone
2015-08-19 22:07 ` [PATCH v2 5/5] ACPI: remove definition of BAD_MADT_ENTRY macro Al Stone

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55F295A7.20406@arm.com \
    --to=sudeep.holla@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).