All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@intel.com>
To: Matt Fleming <matt@console-pimps.org>, linux-efi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Matt Fleming <matt.fleming@intel.com>,
	Matthew Garrett <mjg59@srcf.ucam.org>,
	Borislav Petkov <bp@suse.de>
Subject: Re: [PATCH] x86/efi: Only pass mapped RAM regions to free_bootmem_late()
Date: Thu, 05 Jun 2014 07:43:44 -0700	[thread overview]
Message-ID: <53908220.4030208@intel.com> (raw)
In-Reply-To: <1401974854-7716-1-git-send-email-matt@console-pimps.org>

On 06/05/2014 06:27 AM, Matt Fleming wrote:
> free_bootmem_late() expects to only be passed RAM regions that the
> kernel can access, and that have a corresponding 'struct page'. It's
> possible for regions in the EFI memory map to reside in address ranges
> for which pfn_to_page() doesn't work, for instance when running on an
> i386 system with CONFIG_HIGHMEM=n.

FWIW, I think there are also a bunch of ways to hit this if someone uses
mem=, even on 64-bit.

  reply	other threads:[~2014-06-05 14:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-05 13:27 [PATCH] x86/efi: Only pass mapped RAM regions to free_bootmem_late() Matt Fleming
2014-06-05 13:27 ` Matt Fleming
2014-06-05 14:43 ` Dave Hansen [this message]
     [not found] ` <1401974854-7716-1-git-send-email-matt-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2014-06-05 15:01   ` Alan Cox
2014-06-05 15:01     ` Alan Cox
     [not found]     ` <20140605160102.3c58481e-+KEw/ACL1GZE/aiTQr5FLb0Ud+EcFu5g@public.gmane.org>
2014-06-05 18:07       ` Matt Fleming
2014-06-05 18:07         ` 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=53908220.4030208@intel.com \
    --to=dave.hansen@intel.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bp@suse.de \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt.fleming@intel.com \
    --cc=matt@console-pimps.org \
    --cc=mjg59@srcf.ucam.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.