From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Zachary Amsden <zach@vmware.com>
Cc: Chris Wright <chrisw@sous-sol.org>, Andi Kleen <ak@suse.de>,
"Eric W. Biederman" <ebiederm@xmission.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Crash while mapping memory in pagetable_init() (Was: Re: .config)
Date: Fri, 13 Apr 2007 13:12:56 -0700 [thread overview]
Message-ID: <461FE448.70605@goop.org> (raw)
In-Reply-To: <461FE36D.1050205@vmware.com>
Zachary Amsden wrote:
> Note you can always run out of space; to ensure safety, the init code
> needs to not use a fixed mapping size, it needs to map
> end_kernel_address + pae ? 1808k : 896k, assuming 128M vmalloc hole.
> This could cause problems like running into initrd, however, so might
> require loader changes, or perhaps relocating the initrd. Is the
> solution to just cap the kernel size at some fixed maximum? 6.2M
> appears to be the safe limit for all configurations.
>
> I'm pulling this back onto lkml; seems this is a serious bug which
> needs attention. I've also cc'd some parties that might have relevant
> knowledge. Why do I seem to recall head.S mapping 128M of mappings at
> one point in time?
I just posted a patch. Oops, forgot to Cc: Eric.
J
next prev parent reply other threads:[~2007-04-13 20:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070413174913.GA25234@ezr.goop.org>
[not found] ` <20070413183841.GP10574@sequoia.sous-sol.org>
[not found] ` <20070413190552.GQ10574@sequoia.sous-sol.org>
[not found] ` <461FD97B.1010203@goop.org>
2007-04-13 20:09 ` Crash while mapping memory in pagetable_init() (Was: Re: .config) Zachary Amsden
2007-04-13 20:12 ` Jeremy Fitzhardinge [this message]
2007-04-13 20:26 ` H. Peter Anvin
2007-04-13 20:27 ` Jeremy Fitzhardinge
2007-04-13 20:32 ` H. Peter Anvin
2007-04-13 20:36 ` Jeremy Fitzhardinge
2007-04-13 20:42 ` H. Peter Anvin
2007-04-13 21:05 ` Jeremy Fitzhardinge
2007-04-13 21:12 ` H. Peter Anvin
2007-04-14 0:10 ` Chris Wright
2007-04-13 20:37 ` H. Peter Anvin
2007-04-13 21:07 ` Zachary Amsden
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=461FE448.70605@goop.org \
--to=jeremy@goop.org \
--cc=ak@suse.de \
--cc=chrisw@sous-sol.org \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=zach@vmware.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 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.