On 09/15, Ard Biesheuvel wrote: > On 15 September 2017 at 11:53, Stephen Boyd <[email protected]> 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 <[email protected]> > > > > Reported-by: Stephen Boyd <[email protected]> > > > > I will test early next week and provide a tested-by. Thanks. > > > > Great, thanks. >
Tested-by: Stephen Boyd <[email protected]> -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
