public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Fleming <matt@console-pimps.org>
To: linux-efi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
	Matthew Garrett <mjg59@srcf.ucam.org>,
	Zach Bobroff <zacharyb@ami.com>,
	stable@vger.kernel.org, Matt Fleming <matt.fleming@intel.com>
Subject: Re: [PATCH] x86, efi: retry ExitBootServices() on failure
Date: Tue, 11 Jun 2013 08:22:22 +0100	[thread overview]
Message-ID: <20130611072222.GH31198@console-pimps.org> (raw)
In-Reply-To: <1370933558-10128-1-git-send-email-matt@console-pimps.org>

On Tue, 11 Jun, at 07:52:38AM, Matt Fleming wrote:
> From: Zach Bobroff <zacharyb@ami.com>
> 
> ExitBootServices is absolutely supposed to return a failure if any
> ExitBootServices event handler changes the memory map.  Basically the
> get_map loop should run again if ExitBootServices returns an error the
> first time.  I would say it would be fair that if ExitBootServices gives
> an error the second time then Linux would be fine in returning control
> back to BIOS.
> 
> The second change is the following line:
> 
> again:
>         size += sizeof(*mem_map) * 2;
> 
> Originally you were incrementing it by the size of one memory map entry.
> The issue here is all related to the low_alloc routine you are using.
> In this routine you are making allocations to get the memory map itself.
> Doing this allocation or allocations can affect the memory map by more
> than one record.
> 
> [ mfleming - changelog, code style ]
> Signed-off-by: Zach Bobroff <zacharyb@ami.com>
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Matt Fleming <matt.fleming@intel.com>
> ---
>  arch/x86/boot/compressed/eboot.c | 20 +++++++++++++++++---
>  1 file changed, 17 insertions(+), 3 deletions(-)

I've queued this patch up for v3.11 in my 'next' branch.

-- 
Matt Fleming, Intel Open Source Technology Center

  reply	other threads:[~2013-06-11  7:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-11  6:52 [PATCH] x86, efi: retry ExitBootServices() on failure Matt Fleming
2013-06-11  7:22 ` Matt Fleming [this message]
2013-06-13 16:00 ` joeyli
2013-06-17  9:21   ` Matt Fleming
2013-06-17  9:46     ` Jan Beulich
2013-06-17 10:17       ` Matt Fleming
2013-06-17 10:41         ` joeyli
2013-06-17 11:02         ` Jan Beulich
2013-06-17 12:30           ` Matt Fleming
2013-06-18  0:18             ` Zachary Bobroff
2013-06-18  2:47               ` joeyli
2013-06-18  4:20                 ` Zachary Bobroff
2013-06-18  7:34                   ` joeyli
2013-06-18 13:03               ` Jan Beulich
2013-06-18 22:12                 ` Zachary Bobroff
2013-06-19  8:43                   ` matt
2013-06-19  8:53                     ` H. Peter Anvin
2013-06-20 18:04                       ` Zachary Bobroff
2013-06-26 13:12                         ` matt

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=20130611072222.GH31198@console-pimps.org \
    --to=matt@console-pimps.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt.fleming@intel.com \
    --cc=mjg59@srcf.ucam.org \
    --cc=stable@vger.kernel.org \
    --cc=zacharyb@ami.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