From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Matt Fleming <matt@console-pimps.org>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
Matt Fleming <matt.fleming@intel.com>,
Matthew Garrett <mjg59@srcf.ucam.org>,
Dave Hansen <dave.hansen@intel.com>, Borislav Petkov <bp@suse.de>
Subject: Re: [PATCH] x86/efi: Only pass mapped RAM regions to free_bootmem_late()
Date: Thu, 5 Jun 2014 16:01:02 +0100 [thread overview]
Message-ID: <20140605160102.3c58481e@www.etchedpixels.co.uk> (raw)
In-Reply-To: <1401974854-7716-1-git-send-email-matt@console-pimps.org>
On Thu, 5 Jun 2014 14:27:34 +0100
Matt Fleming <matt@console-pimps.org> wrote:
> From: Matt Fleming <matt.fleming@intel.com>
>
> 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.
>
> This is in fact the case for one of Alan's machines where some of the
> EFI boot services pages live in highmem, and running a kernel without
> CONFIG_HIGHMEM enabled results in the following oops,
>
> BUG: unable to handle kernel paging request at f7f1f080
> IP: [<c17fba96>] __free_pages_bootmem+0x5a/0xb8
> *pdpt = 0000000001887001 *pde = 0000000001984067 *pte = 000000000 0000000
> Oops: 0002 [#1] SMP
No improvement, and the if case is never true 8(
next prev parent reply other threads:[~2014-06-05 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 13:27 Matt Fleming
2014-06-05 14:43 ` Dave Hansen
2014-06-05 15:01 ` Alan Cox [this message]
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=20140605160102.3c58481e@www.etchedpixels.co.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bp@suse.de \
--cc=dave.hansen@intel.com \
--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 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®