All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tom Spink" <tspink@gmail.com>
To: "Jeff Dike" <jdike@addtoit.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: UML fails to locate address space
Date: Tue, 20 May 2008 17:43:17 +0100	[thread overview]
Message-ID: <7b9198260805200943x6fb15512o7ba35a40d006b215@mail.gmail.com> (raw)
In-Reply-To: <20080520161047.GA9598@c2.user-mode-linux.org>

2008/5/20 Jeff Dike <jdike@addtoit.com>:
> On Tue, May 20, 2008 at 02:59:14PM +0100, Tom Spink wrote:
>> Attached.  I guess the line of interest is:
>>
>> mmap2(NULL, 4096, PROT_READ|PROT_WRITE,
>> MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = -1 EACCES (Permission
>> denied)
>
> Yup.
>
> Can you try three things:
>        check the maps file for any arbitrary process
> (i.e. /proc/$$/maps) and see if there's anything mapped at 0

Nothing.

>        gdb UML, stop it at that mmap, check its maps file and see if
> there's anything mapped at 0

Nope.

>        send me a pointer to the patches that Ubuntu has applied on
> top of the stock kernel - I'm suspicious that they special-cased page
> zero in order to ensure that NULL pointer dereferences cause faults.
>
> You can test this last theory by initializing bottom to 4096 instead
> of 0.

I suspected this type of foul-play, and tried altering bottom to 1,
but this didn't work.  So, I took out the page_ok test, and it
continued booting.  So I went back, put the test back in and
incremented bottom until I got to 16.  It worked at 16. :-)

Is this something that can be fixed, or would a config option be appropriate?

I am willing to blame Ubuntu, but unfortunately, I can't find an
online resource of their patches.

>                        Jeff
>
> --
> Work email - jdike at linux dot intel dot com
>

-- 
Tom Spink

  reply	other threads:[~2008-05-20 16:43 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-20 11:08 UML fails to locate address space Tom Spink
2008-05-20 13:52 ` Jeff Dike
2008-05-20 13:59   ` Tom Spink
2008-05-20 16:10     ` Jeff Dike
2008-05-20 16:43       ` Tom Spink [this message]
2008-05-20 17:56         ` Jeff Dike
2008-05-20 18:01           ` Tom Spink
2008-05-20 19:24             ` Jeff Dike
2008-05-20 19:42               ` Tom Spink
2008-05-20 21:27                 ` Jeff Dike
2008-05-20 22:03                   ` Tom Spink
2008-05-20 23:57                     ` Tom Spink
2008-05-21  1:58                       ` Jeff Dike
2008-05-20 15:22   ` linux-os (Dick Johnson)
2008-05-20 17:35     ` Jeff Dike
2008-05-20 21:54       ` linux-os (Dick Johnson)
2008-05-21  2:15         ` Jeff Dike
2008-05-21 12:02           ` Tom Spink
2008-05-21 12:04             ` Tom Spink
2008-05-21 17:58               ` Jeff Dike
2008-05-21 19:01                 ` Tom Spink
2008-05-20 21:58       ` linux-os (Dick Johnson)

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=7b9198260805200943x6fb15512o7ba35a40d006b215@mail.gmail.com \
    --to=tspink@gmail.com \
    --cc=jdike@addtoit.com \
    --cc=linux-kernel@vger.kernel.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.