All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Fleming <matt@console-pimps.org>
To: "H. Peter Anvin" <hpa@linux.intel.com>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org,
	Michel Lespinasse <walken@google.com>
Subject: [GIT PULL] EFI urgent fix
Date: Fri, 26 Apr 2013 17:30:22 +0100	[thread overview]
Message-ID: <20130426163022.GC23038@console-pimps.org> (raw)

Hi Peter, Linus,

I've got a small patch that fixes a crash for the Google folks and their
EFI SMI driver, which was caused by dereferencing a garbage pointer.

Please consider pulling.

The following changes since commit f697036b93aa7345d4cbb3c854a76456c0ddac45:

  efi: Check EFI revision in setup_efi_vars (2013-04-24 16:19:01 +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 45432323ef7038a91599959173700fdb8a0adb2f:

  efivars: only check for duplicates on the registered list (2013-04-26 16:50:01 +0100)

----------------------------------------------------------------
 * Last minute bugfix for the efivars code. The google EFI SMI driver
   maintains its own list of EFI variables but the efivars core was
   directly accessing a different (and in this case, uninitialised) list
   resulting in a crash.

----------------------------------------------------------------
Matt Fleming (1):
      efivars: only check for duplicates on the registered list

 drivers/firmware/efivars.c | 12 +++++++-----
 1 file changed, 7 insertions(+), 5 deletions(-)

-- 
Matt Fleming, Intel Open Source Technology Center

WARNING: multiple messages have this Message-ID (diff)
From: Matt Fleming <matt-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
To: "H. Peter Anvin" <hpa-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
	Linus Torvalds
	<torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Cc: Ingo Molnar <mingo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Michel Lespinasse
	<walken-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Subject: [GIT PULL] EFI urgent fix
Date: Fri, 26 Apr 2013 17:30:22 +0100	[thread overview]
Message-ID: <20130426163022.GC23038@console-pimps.org> (raw)

Hi Peter, Linus,

I've got a small patch that fixes a crash for the Google folks and their
EFI SMI driver, which was caused by dereferencing a garbage pointer.

Please consider pulling.

The following changes since commit f697036b93aa7345d4cbb3c854a76456c0ddac45:

  efi: Check EFI revision in setup_efi_vars (2013-04-24 16:19:01 +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 45432323ef7038a91599959173700fdb8a0adb2f:

  efivars: only check for duplicates on the registered list (2013-04-26 16:50:01 +0100)

----------------------------------------------------------------
 * Last minute bugfix for the efivars code. The google EFI SMI driver
   maintains its own list of EFI variables but the efivars core was
   directly accessing a different (and in this case, uninitialised) list
   resulting in a crash.

----------------------------------------------------------------
Matt Fleming (1):
      efivars: only check for duplicates on the registered list

 drivers/firmware/efivars.c | 12 +++++++-----
 1 file changed, 7 insertions(+), 5 deletions(-)

-- 
Matt Fleming, Intel Open Source Technology Center

             reply	other threads:[~2013-04-26 16:30 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-26 16:30 Matt Fleming [this message]
2013-04-26 16:30 ` [GIT PULL] EFI urgent fix Matt Fleming
2013-04-26 16:40 ` Linus Torvalds
2013-04-26 16:40   ` Linus Torvalds
2013-04-26 16:48   ` Matt Fleming
2013-04-26 16:48     ` Matt Fleming
2013-06-21  9:56 Matt Fleming
2013-06-21  9:56 ` Matt Fleming
2013-09-19 12:41 Matt Fleming
2013-09-19 12:41 ` Matt Fleming
2013-09-20  7:53 ` Ingo Molnar
2013-09-20  7:53   ` Ingo Molnar
2014-03-04 23:47 Matt Fleming
2014-03-04 23:47 ` Matt Fleming
2014-05-03  5:51 Matt Fleming
2014-05-03  5:51 ` Matt Fleming
2014-05-04 18:21 ` Ingo Molnar
2014-05-04 18:21   ` Ingo Molnar
2014-06-20  9:00 Matt Fleming
2014-06-20  9:28 ` Catalin Marinas
2014-06-20  9:28   ` Catalin Marinas
2014-06-20 13:39   ` Leif Lindholm
2014-06-20 13:39     ` Leif Lindholm
2014-06-20 13:49     ` Matt Fleming
2014-06-20 14:19       ` Leif Lindholm
2014-06-25 20:42 ` Matt Fleming
2014-06-25 20:42   ` Matt Fleming
2014-07-07  6:43 Matt Fleming
2014-07-07  6:43 ` Matt Fleming
2014-08-06  9:46 Matt Fleming
2014-08-06  9:46 ` Matt Fleming
2014-09-19 10:33 Matt Fleming
2014-09-19 10:33 ` Matt Fleming
2014-09-19 10:50 ` Ingo Molnar
2015-03-27 19:18 Matt Fleming
2015-06-11 12:47 Matt Fleming
2015-06-11 14:43 ` Ingo Molnar
2015-06-11 14:43   ` Ingo Molnar
2015-06-12 15:00   ` Matt Fleming
2015-06-12 15:00     ` Matt Fleming
2015-07-15 14:31 Matt Fleming
2015-07-21  7:53 ` Ingo Molnar
2015-07-21  7:53   ` Ingo Molnar
2015-10-12 14:13 Matt Fleming
2015-10-16 10:01 Matt Fleming
2015-10-16 10:01 ` Matt Fleming
2015-10-16 10:04 ` Ingo Molnar
2015-10-16 10:04   ` Ingo Molnar
2015-11-04 10:47 Matt Fleming
2015-11-04 10:47 ` Matt Fleming
2015-11-04 10:50 ` Thomas Gleixner
2015-11-04 10:50   ` Thomas Gleixner
2016-04-01 19:03 Matt Fleming
2016-04-02  7:32 ` Ingo Molnar
2016-04-02  7:32   ` Ingo Molnar
2016-04-25 11:26 Matt Fleming
2016-04-25 11:26 ` Matt Fleming
2016-04-25 15:29 ` Ingo Molnar
2016-05-13 20:34 Matt Fleming
2016-05-13 20:34 ` Matt Fleming
2017-01-27 22:06 Matt Fleming
2017-01-27 22:06 ` Matt Fleming
2017-04-12 15:27 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=20130426163022.GC23038@console-pimps.org \
    --to=matt@console-pimps.org \
    --cc=hpa@linux.intel.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=walken@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.