All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, linux-acpi@vger.kernel.org,
	will@kernel.org, catalin.marinas@arm.com, sudeep.holla@arm.com,
	kernel-hardening@lists.openwall.com
Subject: Re: [PATCH v3 0/2] arm64/acpi: restrict AML opregion memory access
Date: Thu, 9 Jul 2020 09:42:36 +0100	[thread overview]
Message-ID: <20200709084236.GA18009@e121166-lin.cambridge.arm.com> (raw)
In-Reply-To: <20200626155832.2323789-1-ardb@kernel.org>

On Fri, Jun 26, 2020 at 05:58:30PM +0200, Ard Biesheuvel wrote:
> v2:
> - do a more elaborate check on the region, against the EFI memory map
> 
> v3:
> - split into two patches
> - fallback to __ioremap() for ACPI reclaim memory, in case it is not covered
>   by the linear mapping (e.g., when booting a kdump kernel)
> 
> Ard Biesheuvel (2):
>   arm64/acpi: disallow AML memory opregions to access kernel memory
>   arm64/acpi: disallow writeable AML opregion mapping for EFI code
>     regions
> 
>  arch/arm64/include/asm/acpi.h | 15 +---
>  arch/arm64/kernel/acpi.c      | 75 ++++++++++++++++++++
>  2 files changed, 76 insertions(+), 14 deletions(-)

Thanks Ard for fixing this, for the series:

Acked-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>

WARNING: multiple messages have this Message-ID (diff)
From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: kernel-hardening@lists.openwall.com, catalin.marinas@arm.com,
	linux-acpi@vger.kernel.org, sudeep.holla@arm.com,
	will@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/2] arm64/acpi: restrict AML opregion memory access
Date: Thu, 9 Jul 2020 09:42:36 +0100	[thread overview]
Message-ID: <20200709084236.GA18009@e121166-lin.cambridge.arm.com> (raw)
In-Reply-To: <20200626155832.2323789-1-ardb@kernel.org>

On Fri, Jun 26, 2020 at 05:58:30PM +0200, Ard Biesheuvel wrote:
> v2:
> - do a more elaborate check on the region, against the EFI memory map
> 
> v3:
> - split into two patches
> - fallback to __ioremap() for ACPI reclaim memory, in case it is not covered
>   by the linear mapping (e.g., when booting a kdump kernel)
> 
> Ard Biesheuvel (2):
>   arm64/acpi: disallow AML memory opregions to access kernel memory
>   arm64/acpi: disallow writeable AML opregion mapping for EFI code
>     regions
> 
>  arch/arm64/include/asm/acpi.h | 15 +---
>  arch/arm64/kernel/acpi.c      | 75 ++++++++++++++++++++
>  2 files changed, 76 insertions(+), 14 deletions(-)

Thanks Ard for fixing this, for the series:

Acked-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2020-07-09  8:42 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-26 15:58 [PATCH v3 0/2] arm64/acpi: restrict AML opregion memory access Ard Biesheuvel
2020-06-26 15:58 ` Ard Biesheuvel
2020-06-26 15:58 ` [PATCH v3 1/2] arm64/acpi: disallow AML memory opregions to access kernel memory Ard Biesheuvel
2020-06-26 15:58   ` Ard Biesheuvel
2020-09-28 16:02   ` Jonathan Cameron
2020-09-28 16:02     ` Jonathan Cameron
2020-09-28 16:49     ` Ard Biesheuvel
2020-09-28 16:49       ` Ard Biesheuvel
2020-09-28 16:49       ` Ard Biesheuvel
2020-09-28 17:17       ` Jonathan Cameron
2020-09-28 17:17         ` Jonathan Cameron
2020-09-29  9:29         ` Ard Biesheuvel
2020-09-29  9:29           ` Ard Biesheuvel
2020-09-29  9:29           ` Ard Biesheuvel
2020-09-30  9:27           ` Jonathan Cameron
2020-09-30  9:27             ` Jonathan Cameron
2020-09-30 17:19             ` Catalin Marinas
2020-09-30 17:19               ` Catalin Marinas
2020-06-26 15:58 ` [PATCH v3 2/2] arm64/acpi: disallow writeable AML opregion mapping for EFI code regions Ard Biesheuvel
2020-06-26 15:58   ` Ard Biesheuvel
2021-02-06  3:11   ` Shawn Guo
2021-02-06  3:11     ` Shawn Guo
2021-02-06  8:10     ` Ard Biesheuvel
2021-02-06  8:10       ` Ard Biesheuvel
2021-02-06  8:10       ` Ard Biesheuvel
2021-02-06 10:17       ` Ard Biesheuvel
2021-02-06 10:17         ` Ard Biesheuvel
2021-02-06 10:17         ` Ard Biesheuvel
2021-02-06 10:45       ` Shawn Guo
2021-02-06 10:45         ` Shawn Guo
2020-07-08 16:17 ` [PATCH v3 0/2] arm64/acpi: restrict AML opregion memory access Ard Biesheuvel
2020-07-08 16:17   ` Ard Biesheuvel
2020-07-08 16:17   ` Ard Biesheuvel
2020-07-09  8:42 ` Lorenzo Pieralisi [this message]
2020-07-09  8:42   ` Lorenzo Pieralisi
2020-07-14 19:52 ` Catalin Marinas

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=20200709084236.GA18009@e121166-lin.cambridge.arm.com \
    --to=lorenzo.pieralisi@arm.com \
    --cc=ardb@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=sudeep.holla@arm.com \
    --cc=will@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.