public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Fleming <matt@codeblueprint.co.uk>
To: Ingo Molnar <mingo@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] EFI urgent fixes
Date: Tue, 5 May 2015 17:27:55 +0100	[thread overview]
Message-ID: <20150505162755.GA3767@codeblueprint.co.uk> (raw)

Folks, please pull the following bug fixes for efivarfs, EFI boot stub
and the EFI runtime map code.

The following changes since commit bfbaafae8519d82d10da6abe75f5766dd5b20475:

  firmware: dmi_scan: Prevent dmi_num integer overflow (2015-03-27 10:53:46 +0000)

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 d67e199611b986b345ea3087ee2e4a15da1c98b3:

  efi: Fix error handling in add_sysfs_runtime_map_entry() (2015-05-05 16:20:13 +0100)

----------------------------------------------------------------
 * Avoid garbage names in efivarfs due to buggy firmware by zero'ing
   EFI variable name - Ross Lagerwall

 * Stop erroneously dropping upper 32-bits of boot command line pointer
   in EFI boot stub and stash them in ext_cmd_line_ptr - Roy Franz

 * Fix double-free bug in error handling code path of EFI runtime map
   code - Dan Carpenter

----------------------------------------------------------------
Dan Carpenter (1):
      efi: Fix error handling in add_sysfs_runtime_map_entry()

Ross Lagerwall (1):
      efivarfs: Ensure VariableName is NUL-terminated

Roy Franz (1):
      x86/efi: Store upper bits of command line buffer address in ext_cmd_line_ptr

 arch/x86/boot/compressed/eboot.c   | 2 ++
 drivers/firmware/efi/runtime-map.c | 6 +++---
 fs/efivarfs/super.c                | 2 +-
 3 files changed, 6 insertions(+), 4 deletions(-)

-- 
Matt Fleming, Intel Open Source Technology Center

             reply	other threads:[~2015-05-05 16:28 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-05 16:27 Matt Fleming [this message]
2015-05-06  6:31 ` [GIT PULL] EFI urgent fixes Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2015-07-30 21:06 Matt Fleming
2015-07-31  7:56 ` 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-07-14 12:54 Matt Fleming
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=20150505162755.GA3767@codeblueprint.co.uk \
    --to=matt@codeblueprint.co.uk \
    --cc=hpa@zytor.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    /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