public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Antoine Martin <antoine@nagafix.co.uk>
Cc: linux-kernel@vger.kernel.org, jdike@addtoit.com
Subject: Re: 2.6.11.8 + UML/x86_64 (2.6.12-rc3+) = oops
Date: Sun, 08 May 2005 17:15:36 +0200	[thread overview]
Message-ID: <m1acn5vjdz.fsf@muc.de> (raw)
In-Reply-To: <1115570102.10373.23.camel@cobra> (Antoine Martin's message of "Sun, 08 May 2005 17:35:02 +0100")

Antoine Martin <antoine@nagafix.co.uk> writes:

>> (..)
>> That is a wrmsr to 0x00000000c0000102 (KERNEL_GS_BASE), the code 
>> is trying to write 0x0000c8e816000002 into it. That is a non canonical
>> address, which causes the GPF.
>> 
>> The strange thing is that the kernel should have rejected it in
>> the first place. The code to allow user space to set kernel gs 
>> checks for the address being > TASK_SIZE and TASK_SIZE is 0x800000000000.
>> It should have rejected it in the first place.
>> 
>> Are you sure you did not apply any strange UML related patches
>> to the host kernel? Maybe those are buggy.
> The only extra patch applied on top of what is on the web page (as per
> Jeff's instructions) is the mconsole-exec patch, and AFAIK it wouldn't
> affect the code above.
>
> Alexander Nyberg is also experiencing crashes, aren't you?


Ok, the bug is found now. It is a kernel bug that it allows to set
non canonical addresses in 64bit segment registers through ptrace.

But even if I fixed that then it will not help you run UML, because
UML needs to set correct addresses of course, not illegal ones.

I will submit a patch later for the crash problem.

-Andi

  reply	other threads:[~2005-05-08 15:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050504191828.620C812EE7@sc8-sf-spam2.sourceforge.net>
     [not found] ` <1115248927.12088.52.camel@cobra>
     [not found]   ` <1115392141.12197.3.camel@cobra>
2005-05-07 16:31     ` 2.6.11.8 + UML/x86_64 (2.6.12-rc3+) = oops Antoine Martin
2005-05-07 15:57       ` Alexander Nyberg
2005-05-07 18:03         ` Jeff Dike
2005-05-08  0:18           ` Al Viro
2005-05-08  6:10             ` Al Viro
2005-05-09 21:07               ` Al Viro
2005-05-10  2:26                 ` Al Viro
2005-05-10  3:50                   ` Jeff Dike
2005-05-10 10:02                     ` Al Viro
2005-05-08 16:28             ` Jeff Dike
2005-05-07 18:06         ` Antoine Martin
2005-05-08 14:12       ` Andi Kleen
2005-05-08 16:35         ` Antoine Martin
2005-05-08 15:15           ` Andi Kleen [this message]
2005-05-08 16:42             ` Jeff Dike
2005-05-08 17:38             ` Antoine Martin
2005-05-08 16:45           ` Jeff Dike
2005-05-08 19:51             ` Antoine Martin
2005-05-08 16:38         ` Jeff Dike

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=m1acn5vjdz.fsf@muc.de \
    --to=ak@muc.de \
    --cc=antoine@nagafix.co.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox