On Fri, May 17, 2013 at 02:05:33PM -0700, Andy Lutomirski wrote:
> The MSI MS-7760 supplies a BGRT marked "invalid" that contains a
> pointer to nowhere. Since an "invalid" BGRT isn't particularly
> useful (userspace isn't supposed to use it anyway), ignore the BGRT
> if it's marked "invalid" and the pointer points outside of EFI boot
> services space.
>
> Signed-off-by: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
I'd suggest generalizing the comment to not just mention the one system
you observed it on. In any case, I'm fine with this patch, but I seem
to recall Matthew Garrett having some objections to ignoring the BGRT
when the valid bit is not set. Also, if you're going to do so, you
might as well not expose the valid bit to userspace.
> This seems to fix the problem for me.
>
> arch/x86/platform/efi/efi-bgrt.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/arch/x86/platform/efi/efi-bgrt.c b/arch/x86/platform/efi/efi-bgrt.c
> index 7145ec6..c77b7cf 100644
> --- a/arch/x86/platform/efi/efi-bgrt.c
> +++ b/arch/x86/platform/efi/efi-bgrt.c
> @@ -49,6 +49,18 @@ void __init efi_bgrt_init(void)
>
> image = efi_lookup_mapped_addr(bgrt_tab->image_address);
> if (!image) {
> + if (!(bgrt_tab->status & 1)) {
> + /*
> + * The MSI MS-7760 exposes an "invalid" BGRT
> + * containing a pointer to nowhere. This heuristic
> + * will avoid following that pointer. (The idea
> + * is that an "invalid" image pointing into boot
> + * services data is probably sensible, but other
> + * "invalid" pointers are questionable.)
> + */
> + return;
> + }
> +
> image = ioremap(bgrt_tab->image_address, sizeof(bmp_header));
> ioremapped = true;
> if (!image)
> --
> 1.8.1.4
>
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
