public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Is SKAS still required for UML
Date: Wed, 27 Aug 2008 15:06:55 -0400	[thread overview]
Message-ID: <20080827190655.GB12522@c2.user-mode-linux.org> (raw)
In-Reply-To: <alpine.LNX.1.10.0808271251170.1378@fbirervta.pbzchgretzou.qr>

On Wed, Aug 27, 2008 at 12:57:53PM -0400, Jan Engelhardt wrote:
> the UML page at http://user-mode-linux.sourceforge.net/old/skas.html 
> mentions that "The UML kernel is present in the address space of each of 
> its processes, and, by default, is writeable".

That stuff, as you can see by the "old" in the URL, is old.

Since skas0 became the default, that statement is no longer true.
> 
> I tried to put this to a test, and actually failed to modify the 
> UML kernel/memory image from within it. I had a simple kernel module 
> with 'int val = 2;' and upon loading this, done printk("Val is at %p\n", 
> &val); to get to know the address. A userspace program inside the UML 
> then tried to dereference that address and read the value, but that 
> ended in a segfault. /proc/xxx/maps also does not show the UML kernel 
> being mapped in any process inside the UML. Note that I was running in 
> SKAS0 mode, both host and guest are all 64-bit. Is the NX bit of the 
> 64-bit platform securing things off, or has SKAS3 become sort of 
> obsolete?

SKAS3 is still a significant performance boost.

      	       		     Jeff

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

  reply	other threads:[~2008-08-27 19:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-27 16:57 Is SKAS still required for UML Jan Engelhardt
2008-08-27 19:06 ` Jeff Dike [this message]
2008-08-27 20:00   ` Jan Engelhardt
2008-08-27 21:03     ` Jeff Dike
2008-08-30 11:46   ` Nix
  -- strict thread matches above, loose matches on Subject: below --
2008-09-05 13:36 greg

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=20080827190655.GB12522@c2.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=jengelh@medozas.de \
    --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