public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Fleming <matt@console-pimps.org>
To: "H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@kernel.org>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] EFI urgent fixes
Date: Mon, 14 Jul 2014 13:54:32 +0100	[thread overview]
Message-ID: <20140714125432.GI5952@console-pimps.org> (raw)

Folks, please pull the following urgent fixes. Of particular importance
is the patch from Michael that fixes a memory corruption bug in the x86
EFI boot stub.

The following changes since commit 783ee43118dc773bc8b0342c5b230e017d5a04d0:

  efi-pstore: Fix an overflow on 32-bit builds (2014-06-27 07:30:32 +0100)

are available in the git repository at:

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

for you to fetch changes up to c7fb93ec51d462ec3540a729ba446663c26a0505:

  x86/efi: Include a .bss section within the PE/COFF headers (2014-07-10 14:21:39 +0100)

----------------------------------------------------------------
 * Remove a duplicate copy of linux_banner from the arm64 EFI stub
   which, apart from reducing code duplication also stops the arm64 stub
   being rebuilt every time make is invoked - Ard Biesheuvel

 * Fix the EFI fdt code to not report a boot error if UEFI is
   unavailable since booting without UEFI parameters is a valid use case
   for non-UEFI platforms - Catalin Marinas

 * Include a .bss section in the EFI boot stub PE/COFF headers to fix a
   memory corruption bug - Michael Brown

----------------------------------------------------------------
Ard Biesheuvel (1):
      efi/arm64: efistub: remove local copy of linux_banner

Catalin Marinas (1):
      efi: fdt: Do not report an error during boot if UEFI is not available

Michael Brown (1):
      x86/efi: Include a .bss section within the PE/COFF headers

 arch/arm64/kernel/efi-stub.c |  2 --
 arch/x86/boot/header.S       | 26 ++++++++++++++++++++++----
 arch/x86/boot/tools/build.c  | 38 ++++++++++++++++++++++++++++++--------
 drivers/firmware/efi/efi.c   | 22 +++++++++++++++-------
 drivers/firmware/efi/fdt.c   | 10 ----------
 5 files changed, 67 insertions(+), 31 deletions(-)

-- 
Matt Fleming, Intel Open Source Technology Center

             reply	other threads:[~2014-07-14 12:54 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-14 12:54 Matt Fleming [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-07-30 21:06 [GIT PULL] EFI urgent fixes Matt Fleming
2015-07-31  7:56 ` Ingo Molnar
2015-05-05 16:27 Matt Fleming
2015-05-06  6:31 ` Ingo Molnar
2015-03-02 12:51 Matt Fleming
2015-03-02 13:24 ` Ingo Molnar
2015-03-02 13:35   ` Matt Fleming
2015-02-18 11:55 Matt Fleming
2015-02-18 13:43 ` Ingo Molnar
2015-02-18 16:36   ` Ard Biesheuvel
2015-02-18 16:57     ` Ingo Molnar
2014-09-25  7:31 Matt Fleming
2014-09-25 14:41 ` Ingo Molnar
2014-09-25 14:44   ` Matt Fleming
2014-09-26 11:27   ` Paul Bolle
2014-09-26 11:35     ` Ingo Molnar
2014-09-26 12:24       ` Matt Fleming
2014-09-27  5:49         ` Ingo Molnar
2014-09-26 11:44     ` Matt Fleming
2014-09-26 11:59       ` Paul Bolle
2014-09-26 12:34         ` Matt Fleming
2014-09-26 12:55           ` Paul Bolle
2014-09-27  8:04           ` Valentin Rothberg
2014-09-27  9:59             ` Paul Bolle
2014-09-08 21:55 Matt Fleming
2014-09-09  5:07 ` Ingo Molnar
2014-09-09  7:07   ` Matt Fleming
2014-09-09 14:55     ` Ingo Molnar
2014-08-22  7:52 Matt Fleming
2014-08-22  8:15 ` Ingo Molnar
2014-06-27 14:51 Matt Fleming
2014-06-04 16:53 Matt Fleming
2014-04-11  7:16 Matt Fleming
2014-04-11  8:27 ` Ingo Molnar
2014-02-14 13:08 Matt Fleming
2013-11-29 12:09 Matt Fleming
2013-07-11 11:16 Matt Fleming
2013-06-07 11:50 Matt Fleming
2013-06-10 21:36 ` Matt Fleming
2013-05-17 10:18 Matt Fleming
2013-04-25  8:49 Matt Fleming

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=20140714125432.GI5952@console-pimps.org \
    --to=matt@console-pimps.org \
    --cc=hpa@zytor.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox