linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: linux-efi@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H . Peter Anvin" <hpa@zytor.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	linux-kernel@vger.kernel.org, Dave Young <dyoung@redhat.com>,
	Maniaxx <tripleshiftone@gmail.com>,
	Matt Fleming <matt@codeblueprint.co.uk>
Subject: [GIT PULL] Another EFI BGRT fix for v4.12
Date: Fri,  9 Jun 2017 08:45:57 +0000	[thread overview]
Message-ID: <20170609084558.26766-1-ard.biesheuvel@linaro.org> (raw)

The following changes since commit 7425826f4f7ac60f2538b06a7f0a5d1006405159:

  efi/bgrt: Skip efi_bgrt_init() in case of non-EFI boot (2017-05-28 11:06:17 +0200)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git tags/efi-urgent

for you to fetch changes up to 0a97e704d93fe4facf2bffe3c78095b9d441df42:

  efi: fix boot panic because of invalid bgrt image address (2017-06-09 08:38:49 +0000)

----------------------------------------------------------------
Another BGRT regression fix from Dave Young, to avoid a crash on buggy
firmware that puts a bogus image address in the BGRT table.

----------------------------------------------------------------
Dave Young (1):
      efi: fix boot panic because of invalid bgrt image address

 drivers/firmware/efi/efi-bgrt.c | 26 +++++++++++++++++++++++++-
 1 file changed, 25 insertions(+), 1 deletion(-)

             reply	other threads:[~2017-06-09  8:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-09  8:45 Ard Biesheuvel [this message]
2017-06-09  8:45 ` [PATCH] efi: fix boot panic because of invalid bgrt image address Ard Biesheuvel
2017-06-09 18:25   ` [tip:efi/urgent] efi: Fix boot panic because of invalid BGRT " tip-bot for Dave Young

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=20170609084558.26766-1-ard.biesheuvel@linaro.org \
    --to=ard.biesheuvel@linaro.org \
    --cc=dyoung@redhat.com \
    --cc=hpa@zytor.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@codeblueprint.co.uk \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tripleshiftone@gmail.com \
    /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).