From: Ingo Molnar <mingo@elte.hu>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Alexander Viro <viro@math.psu.edu>
Subject: Re: 4GB+DEBUG_PAGEALLOC oopses with 2.6.0-test3-mm1
Date: Mon, 11 Aug 2003 17:24:49 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.56.0308111723040.11173@localhost.localdomain> (raw)
In-Reply-To: <3F37B4B7.9010108@colorfullife.com>
On Mon, 11 Aug 2003, Manfred Spraul wrote:
> >(in theory it's possible that kernel-internal mounts pass in a pointer
> >where pointer + PAGE_SIZE is not a valid kernel address - if this happens
> >then we'd get a hard crash.)
> Exactly that happens.
> I'm running with CONFIG_PAGE_DEBUG, i.e. unallocated pages are marked as
> non-present in the linear mapping.
this is not a bug technically, unless the mount options are in the last
linearly mapped page. It is a bug to copy those unallocated bytes, but
they do not get to relied upon. Note that the non-4G code copies them just
as much.
> Regarding the i386 trap handler: show_registers tries to hexdump the
> current instructions. It did a __get_user, to avoid causing a fault when
> %eip is invalid.
> Now it contains:
>
> > if ((user_mode(regs) && get_user(c, eip)) ||
> > (!user_mode(regs) && __direct_get_user(c, eip))) {
> > printk(" Bad EIP value.");
> > break;
> > }
>
> I.e. it's already fixed.
yeah, this was one of the latest patches that went into Andrew's tree.
(This fix enabled us to get rid of the do_page_fault() hacks.)
Ingo
next prev parent reply other threads:[~2003-08-11 15:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-10 10:33 Manfred Spraul
2003-08-11 8:56 ` Ingo Molnar
2003-08-11 15:22 ` Manfred Spraul
2003-08-11 15:24 ` Ingo Molnar [this message]
2003-08-11 16:05 ` Manfred Spraul
2003-08-11 17:19 ` Ingo Molnar
2003-08-11 18:01 ` Manfred Spraul
2003-08-11 9:00 ` Ingo Molnar
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=Pine.LNX.4.56.0308111723040.11173@localhost.localdomain \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=viro@math.psu.edu \
/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®