From: lorenzo.pieralisi@arm.com (Lorenzo Pieralisi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] arm64: acpi: Prepare for longer MADTs
Date: Thu, 1 Nov 2018 11:31:36 +0000 [thread overview]
Message-ID: <20181101113136.GA6608@e107981-ln.cambridge.arm.com> (raw)
In-Reply-To: <20181012192937.3819951-1-jeremy.linton@arm.com>
On Fri, Oct 12, 2018 at 02:29:37PM -0500, Jeremy Linton wrote:
> The BAD_MADT_GICC_ENTRY check is a little too strict because
> it rejects MADT entries that don't match the currently known
> lengths. We should remove this restriction to avoid problems
> if the table length changes. Future code which might depend on
> additional fields should be written to validate those fields
> before using them, rather than trying to globally check
> known MADT version lengths.
>
> Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
> ---
> arch/arm64/include/asm/acpi.h | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
Hi Jeremy,
I assume there is no [PATCH 1/2] (to make sure I have not missed
anything).
> diff --git a/arch/arm64/include/asm/acpi.h b/arch/arm64/include/asm/acpi.h
> index 709208dfdc8b..4d0946bd485a 100644
> --- a/arch/arm64/include/asm/acpi.h
> +++ b/arch/arm64/include/asm/acpi.h
> @@ -22,12 +22,12 @@
> #include <asm/tlbflush.h>
>
> /* Macros for consistency checks of the GICC subtable of MADT */
> -#define ACPI_MADT_GICC_LENGTH \
> - (acpi_gbl_FADT.header.revision < 6 ? 76 : 80)
> +#define ACPI_MADT_GICC_MIN_LENGTH ACPI_OFFSET( \
> + struct acpi_madt_generic_interrupt, efficiency_class)
I would add a comment explaining why the efficiency_class offset
corresponds to the min length, I will do it myself before sending it
upstream.
I will take this patch and send it to Will/Catalin with ARM64 ACPI
material for v4.21.
Thanks,
Lorenzo
>
> #define BAD_MADT_GICC_ENTRY(entry, end) \
> - (!(entry) || (entry)->header.length != ACPI_MADT_GICC_LENGTH || \
> - (unsigned long)(entry) + ACPI_MADT_GICC_LENGTH > (end))
> + (!(entry) || (entry)->header.length < ACPI_MADT_GICC_MIN_LENGTH || \
> + (unsigned long)(entry) + (entry)->header.length > (end))
>
> /* Basic configuration for ACPI */
> #ifdef CONFIG_ACPI
> --
> 2.14.3
>
next prev parent reply other threads:[~2018-11-01 11:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 19:29 [PATCH 2/2] arm64: acpi: Prepare for longer MADTs Jeremy Linton
2018-10-15 9:29 ` Sudeep Holla
2018-11-01 11:31 ` Lorenzo Pieralisi [this message]
2018-11-01 14:22 ` Sudeep Holla
2018-11-27 15:01 ` Lorenzo Pieralisi
2018-11-27 16:32 ` Jeremy Linton
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=20181101113136.GA6608@e107981-ln.cambridge.arm.com \
--to=lorenzo.pieralisi@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