All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Fleming <matt-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
To: Michael Brown <mbrown-OViyBiuKJBuK421+ScFKDQ@public.gmane.org>
Cc: linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	"H. Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>,
	"Thomas Bächler" <thomas-fd97jBR+K/6hPH1hqNUYSQ@public.gmane.org>
Subject: Re: [PATCH] efi: Include a .bss section within the PE/COFF headers
Date: Thu, 10 Jul 2014 11:34:31 +0100	[thread overview]
Message-ID: <20140710103431.GE15932@console-pimps.org> (raw)
In-Reply-To: <1404942094-29447-1-git-send-email-mbrown-OViyBiuKJBuK421+ScFKDQ@public.gmane.org>

On Wed, 09 Jul, at 10:41:34PM, Michael Brown wrote:
> The PE/COFF headers currently describe only the initialised-data
> portions of the image, and result in no space being allocated for the
> uninitialised-data portions.  Consequently, the EFI boot stub will end
> up overwriting unexpected areas of memory, with unpredictable results.
> 
> Fix by including a .bss section in the PE/COFF headers (functionally
> equivalent to the init_size field in the bzImage header).
> 
> Signed-off-by: Michael Brown <mbrown-OViyBiuKJBuK421+ScFKDQ@public.gmane.org>
> ---
>  arch/x86/boot/header.S      | 26 ++++++++++++++++++++++----
>  arch/x86/boot/tools/build.c | 37 +++++++++++++++++++++++++++++--------
>  2 files changed, 51 insertions(+), 12 deletions(-)

Yeah ouch, that's a particularly bad bug. Thanks Michael, this fix looks
great.

I've placed this in the urgent EFI queue and tagged it for stable.

Thomas, the patch in question is here this one,

  http://git.kernel.org/cgit/linux/kernel/git/mfleming/efi.git/commit/?h=urgent&id=db0f1ff0ee1750cc52ead0ba1ddf95c47b3bd133

it would be good if you could carry it in archlinux for some additional
testing. I suspect this fix may solve some of the problems people have
reported in,

  https://bugzilla.kernel.org/show_bug.cgi?id=68761

Let me know if you'd like a backported version.

-- 
Matt Fleming, Intel Open Source Technology Center

  parent reply	other threads:[~2014-07-10 10:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-09 21:41 [PATCH] efi: Include a .bss section within the PE/COFF headers Michael Brown
     [not found] ` <1404942094-29447-1-git-send-email-mbrown-OViyBiuKJBuK421+ScFKDQ@public.gmane.org>
2014-07-09 22:20   ` Michael Brown
     [not found]     ` <53BDC038.1090003-OViyBiuKJBuK421+ScFKDQ@public.gmane.org>
2014-07-09 22:41       ` H. Peter Anvin
2014-07-10 10:34   ` Matt Fleming [this message]
     [not found]     ` <20140710103431.GE15932-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2014-07-10 14:48       ` Matt Fleming
     [not found]         ` <20140710144815.GG15932-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2014-07-11 17:22           ` Thomas Bächler
  -- strict thread matches above, loose matches on Subject: below --
2014-07-28 13:21 Michael Brown
     [not found] ` <1406553713-7479-1-git-send-email-mbrown-OViyBiuKJBuK421+ScFKDQ@public.gmane.org>
2014-07-28 22:54   ` H. Peter Anvin
2014-07-30 13:57   ` Luis Henriques

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=20140710103431.GE15932@console-pimps.org \
    --to=matt-hnk1s37rvnbexh+ff434mdi2o/jbrioy@public.gmane.org \
    --cc=hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org \
    --cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mbrown-OViyBiuKJBuK421+ScFKDQ@public.gmane.org \
    --cc=thomas-fd97jBR+K/6hPH1hqNUYSQ@public.gmane.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 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.