From: Blaisorblade <blaisorblade_spam@yahoo.it>
To: William Stearns <wstearns@pobox.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] skas mode on a non-skas host
Date: Tue, 30 Nov 2004 17:10:15 +0100 [thread overview]
Message-ID: <200411301710.15691.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <Pine.LNX.4.58.0411291623340.5077@sparrow>
On Monday 29 November 2004 22:26, William Stearns wrote:
> Good afternoon, Jeff,
>
> On Mon, 29 Nov 2004, Jeff Dike wrote:
> > Prompted by some questions from Blaisorblade about whether something like
> > skas mode might be implemented on unpatched hosts, I went ahead and did
> > exactly that.
> >
> > The basic idea is that in place of /proc/mm and PTRACE_FAULTINFO, we have
> > a couple of extra pages in the userspace process to hold code that we are
> > going to use to make it change its address space and to handle segfaults
> > so addresses and access modes can be reported back to the kernel process.
> >
> > The end result is something that is very close to skas mode, just as
> > secure, loses two pages of address space to UML rather than .5G, should
> > be almost as fast, and runs on a stock host kernel.
> >
> > The patch is available as skas0 from my patches page -
> > http://user-mode-linux.sourceforge.net/patches.html
> > and there is a good deal of commentary associated with it.
>
> /me drops jaw.... :-)
>
> Nice work to both of you - I'm sincerely impressed. Jeff, is
> there a place to grab a "all current 2.6 patches as a single patch" so I
> can give it a try? Or do I need to grab all the 2.6 patches off the
> sourceforge page and just apply them one at a time?
Search "Auto-updating Jeff Dike tree" in uml-devel and take the script from
Frank Sorenson in that thread, to download them less painfully - to apply
them, you'd probably want to download and use quilt or patch-scripts.
With patch-scripts (which I use locally) pushpatch 50 is the command which
applies the next 50 patches (and the list of applied patches is saved, so you
can easily go back and forth in the patch stack.
I don't know the quilt syntax but it won't be totally different - it seems it
is "quilt push 50".
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-11-30 16:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 22:50 [uml-devel] skas mode on a non-skas host Jeff Dike
[not found] ` <Pine.LNX.4.58.0411291623340.5077@sparrow>
2004-11-30 16:10 ` Blaisorblade [this message]
2004-11-30 17:20 ` Gerd Knorr
[not found] ` <200411301912.21155.blaisorblade_spam@yahoo.it>
[not found] ` <41ACB90C.7070209@fujitsu-siemens.com>
2004-11-30 19:02 ` Skas0 security problems (was: Re: [uml-devel] skas mode on a non-skas host) Blaisorblade
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=200411301710.15691.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=wstearns@pobox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox