linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: efi: ignore EFI_MEMORY_XP attribute if RP and/or WP are set
Date: Fri, 22 Sep 2017 14:57:23 -0700	[thread overview]
Message-ID: <20170922215723.GE457@codeaurora.org> (raw)
In-Reply-To: <CAKv+Gu_YEZAZL7X5oE9nPnoYi31xsrktLoik8_Gt442AsaLhWQ@mail.gmail.com>

On 09/15, Ard Biesheuvel wrote:
> On 15 September 2017 at 11:53, Stephen Boyd <sboyd@codeaurora.org> wrote:
> > On 09/14, Ard Biesheuvel wrote:
> >> The UEFI memory map is a bit vague about how to interpret the
> >> EFI_MEMORY_XP attribute when it is combined with EFI_MEMORY_RP and/or
> >> EFI_MEMORY_WP, which have retroactively been redefined as cacheability
> >> attributes rather than permission attributes.
> >>
> >> So let's ignore EFI_MEMORY_XP if _RP and/or _WP are also set. In this
> >> case, it is likely that they are being used to describe the capability
> >> of the region (i.e., whether it has the controls to reconfigure it as
> >> non-executable) rather than the nature of the contents of the region
> >> (i.e., whether it contains data that we will never attempt to execute)
> >>
> >> Cc: Stephen Boyd <sboyd@codeaurora.org>
> >
> > Reported-by: Stephen Boyd <sboyd@codeaurora.org>
> >
> > I will test early next week and provide a tested-by. Thanks.
> >
> 
> Great, thanks.
>

Tested-by: Stephen Boyd <sboyd@codeaurora.org>

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

      reply	other threads:[~2017-09-22 21:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-14 19:31 [PATCH] arm64: efi: ignore EFI_MEMORY_XP attribute if RP and/or WP are set Ard Biesheuvel
2017-09-14 19:33 ` Ard Biesheuvel
2017-09-15 18:53 ` Stephen Boyd
2017-09-15 22:50   ` Ard Biesheuvel
2017-09-22 21:57     ` Stephen Boyd [this message]

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=20170922215723.GE457@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --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).