From: Josh Triplett <josh@joshtriplett.org>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Matt Fleming <matt@console-pimps.org>,
jerry.hoemann@hp.com, Andrew Fish <afish@apple.com>,
edk2-devel@lists.sourceforge.net, linux-efi@vger.kernel.org,
Gleb Natapov <gleb@redhat.com>,
lkml <linux-kernel@vger.kernel.org>,
David Woodhouse <dwmw2@infradead.org>,
Matthew Garrett <mjg59@srcf.ucam.org>,
Brian Richardson <brian.richardson@intel.com>,
Colin Ian King <colin.king@canonical.com>,
Randy Wright <rwright@hp.com>,
Linn Crosetto <linn.crosetto@hp.com>,
terry.lee@hp.com, samer.el-haj-mahmoud@hp.com,
randy.pawell@hp.com, chrisp@hp.com, linda.knippers@hp.com,
dong.wei@hp.com, "H. Peter Anvin" <hpa@zytor.com>,
Borislav Petkov <bp@alien8.de>,
Chao Zhang <chao.b.zhang@intel.com>,
Yao Jiewen <jiewen.yao@intel.com>
Subject: Re: [edk2] Corrupted EFI region
Date: Mon, 16 Sep 2013 09:29:54 -0700 [thread overview]
Message-ID: <20130916162918.GA4555@leaf> (raw)
In-Reply-To: <523730F2.40408@redhat.com>
On Mon, Sep 16, 2013 at 06:25:22PM +0200, Laszlo Ersek wrote:
> On 09/16/13 17:57, Josh Triplett wrote:
>
> >> The edk2 commit that flipped the memory type underneath the image data
> >> from EfiReservedMemoryType to EfiBootServicesData is:
> >>
> >> https://github.com/tianocore/edk2/commit/4c58575e
> >>
> >> I think this commit is wrong. It's fine for OSPM to release the image
> >> data at some point, but not right after ExitBootServices(), because
> >> referencing pointers in ACPI tables survive strictly longer.
> >>
> >> ... Actually, the commit does follow the ACPI spec 5.0:
> >>
> >> 5.2.22.4 Image Address
> >>
> >> The Image Address contains the location in memory where an
> >> in-memory copy of the boot image can be found. The image should be
> >> stored in EfiBootServicesData, allowing the system to reclaim
> >> the memory when the image is no longer needed.
> >>
> >> The ACPI spec 5.0 should recommend EfiACPIReclaimMemory here IMO. (I
> >> take the current wording ("should be stored") as a recommendation only.)
> >
> > I agree that UEFI *should* store the BGRT in EfiACPIReclaimMemory, but
> > in practice the UEFI firmware I've seen with a BGRT does follow that
> > recommendation and store it in EfiBootServicesData. So, even if the
> > recommendation in the spec changed, the kernel would still have to
> > accomodate both possibilities.
>
> Just for the theoretical debate:
>
> The edk2 commit linked above is 5 days old. All UEFI firmware in the
> wild (on released hardware) should be using EfiReservedMemoryType (the
> pre-patch memory type), which is even stricter.
>
> EfiReservedMemoryType can never be released & repurposed, so it should
> make no difference for crash kernel allocation, shouldn't it?
>
> - call efi_free_boot_services() -- doesn't touch the image data (which
> is in RAM of EfiReservedMemoryType),
> - reserve crash kernel,
> - access BGRT via ACPI.
>
> BGRT had appeared in edk2 with
>
> https://github.com/tianocore/edk2/commit/0284e90c
>
> and EfiReservedMemoryType used to be the allocation type until commit
> 4c58575e.
>
> Or are you alluding to UEFI firmware that's not based on TianoCore?
I'm saying, in practice, that the systems I tested BGRT support on and
submitted patches for stored the BGRT's image in EfiBootServicesData.
- Josh Triplett
next prev parent reply other threads:[~2013-09-16 16:30 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 20:54 Corrupted EFI region Borislav Petkov
2013-07-31 20:58 ` Matthew Garrett
2013-07-31 21:51 ` Borislav Petkov
2013-07-31 21:54 ` Matthew Garrett
2013-08-01 16:51 ` Borislav Petkov
2013-07-31 21:55 ` David Woodhouse
2013-08-01 16:49 ` Borislav Petkov
2013-08-05 11:27 ` [edk2] " Laszlo Ersek
2013-08-05 13:02 ` Borislav Petkov
2013-08-05 13:39 ` Laszlo Ersek
2013-08-05 14:03 ` Borislav Petkov
2013-08-05 14:27 ` Laszlo Ersek
2013-08-05 14:40 ` Borislav Petkov
2013-08-05 15:15 ` Laszlo Ersek
2013-08-05 15:34 ` James Bottomley
2013-08-05 16:27 ` Laszlo Ersek
2013-08-05 16:12 ` Borislav Petkov
2013-08-05 16:41 ` Laszlo Ersek
2013-08-05 16:47 ` Borislav Petkov
2013-08-05 17:00 ` Kinney, Michael D
2013-08-05 17:09 ` Laszlo Ersek
2013-08-05 21:26 ` Laszlo Ersek
2013-08-05 22:08 ` Borislav Petkov
2013-08-06 14:10 ` Borislav Petkov
2013-08-06 15:31 ` Laszlo Ersek
2013-08-07 15:19 ` Borislav Petkov
2013-08-07 17:23 ` Andrew Fish
2013-08-07 20:19 ` Matt Fleming
2013-08-07 20:24 ` Matt Fleming
2013-08-07 21:10 ` Andrew Fish
2013-08-07 21:23 ` Matthew Garrett
2013-08-08 10:17 ` Matt Fleming
2013-08-08 13:46 ` Andrew Fish
2013-09-02 8:19 ` Matt Fleming
2013-09-13 20:38 ` jerry.hoemann
2013-09-16 10:59 ` Matt Fleming
2013-09-16 11:50 ` Laszlo Ersek
2013-09-16 15:57 ` Josh Triplett
2013-09-16 16:25 ` Laszlo Ersek
2013-09-16 16:27 ` Matthew Garrett
2013-09-16 16:29 ` Josh Triplett [this message]
2013-09-18 19:24 ` jerry.hoemann
2013-09-20 9:06 ` Matt Fleming
2013-08-07 17:49 ` Laszlo Ersek
2013-08-08 15:02 ` Borislav Petkov
2013-08-08 21:45 ` Brian J. Johnson
2013-08-18 7:33 ` Jordan Justen
2013-08-05 15:50 ` Andrew Fish
2013-08-05 18:12 ` Borislav Petkov
2013-08-05 21:37 ` H. Peter Anvin
2013-08-05 21:41 ` Borislav Petkov
2013-08-05 21:49 ` H. Peter Anvin
2013-08-05 21:55 ` Laszlo Ersek
2013-08-05 22:52 ` James Bottomley
2013-08-06 7:26 ` Laszlo Ersek
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=20130916162918.GA4555@leaf \
--to=josh@joshtriplett.org \
--cc=afish@apple.com \
--cc=bp@alien8.de \
--cc=brian.richardson@intel.com \
--cc=chao.b.zhang@intel.com \
--cc=chrisp@hp.com \
--cc=colin.king@canonical.com \
--cc=dong.wei@hp.com \
--cc=dwmw2@infradead.org \
--cc=edk2-devel@lists.sourceforge.net \
--cc=gleb@redhat.com \
--cc=hpa@zytor.com \
--cc=jerry.hoemann@hp.com \
--cc=jiewen.yao@intel.com \
--cc=lersek@redhat.com \
--cc=linda.knippers@hp.com \
--cc=linn.crosetto@hp.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@console-pimps.org \
--cc=mjg59@srcf.ucam.org \
--cc=randy.pawell@hp.com \
--cc=rwright@hp.com \
--cc=samer.el-haj-mahmoud@hp.com \
--cc=terry.lee@hp.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