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,
Catalin Marinas <catalin.marinas@arm.com>,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] EFI urgent fixes
Date: Fri, 27 Jun 2014 15:51:46 +0100 [thread overview]
Message-ID: <20140627145146.GB7539@console-pimps.org> (raw)
Guys,
Please pull the following EFI fixes. The fix from Catalin is the same as
the one I sent a week ago and Andrzej's patch fixes an efi-pstore issue
on 32-bit machines where efi-pstore variables don't appear in the
filesystem and so can never be deleted, potentially leading to
exhaustion of NVRAM space.
The following changes since commit 7171511eaec5bf23fb06078f59784a3a0626b38f:
Linux 3.16-rc1 (2014-06-15 17:45:28 -1000)
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 783ee43118dc773bc8b0342c5b230e017d5a04d0:
efi-pstore: Fix an overflow on 32-bit builds (2014-06-27 07:30:32 +0100)
----------------------------------------------------------------
* Fix a few compiler warnings (one being a real bug) in the arm64 EFI
code that lots of people are running into and reporting - Catalin Marinas
* Use a cast to avoid a 32-bit overflow issue when generating pstore
filenames - Andrzej Zaborowski
----------------------------------------------------------------
Andrzej Zaborowski (1):
efi-pstore: Fix an overflow on 32-bit builds
Catalin Marinas (1):
efi: Fix compiler warnings (unused, const, type)
drivers/firmware/efi/efi-pstore.c | 2 +-
drivers/firmware/efi/efi.c | 6 +++---
drivers/firmware/efi/fdt.c | 2 +-
3 files changed, 5 insertions(+), 5 deletions(-)
--
Matt Fleming, Intel Open Source Technology Center
next reply other threads:[~2014-06-27 14:51 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 14:51 Matt Fleming [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-07-30 21:06 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-07-14 12:54 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=20140627145146.GB7539@console-pimps.org \
--to=matt@console-pimps.org \
--cc=catalin.marinas@arm.com \
--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
all inboxes | Powered by JetHome®