From: Steven Pritchard <steve@kspei.com>
To: Matthew Bloch <matthew-list@bytemark.co.uk>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] [PATCH] Locking user-mode kernel RAM into host physical RAM
Date: Mon, 8 Dec 2003 12:02:50 -0600 [thread overview]
Message-ID: <20031208180250.GA7787@osiris.silug.org> (raw)
In-Reply-To: <200312081639.22888.matthew-list@bytemark.co.uk>
On Mon, Dec 08, 2003 at 04:39:08PM +0000, Matthew Bloch wrote:
> I hope that it's obvious enough to warrant inclusion in the next release of
> the UML patch; my only thought was whether instead of putting
> setuid-requiring code into the kernel, mem= should accept a file descriptor
> as an argument and have the memory mapping optionally done by an external
> process. This strikes me as a bit weird from most angles, but obviously it
> allows isolation of code which needs root privileges, and would probably be
> very little work to add to the filemap patch for this purpose.
I've long thought that it would be Really Nice if UML could do some
setup things (like this, chroot(), etc.) that need to be done as root
early on, then drop privileges and continue normally.
I once worked on a patch to add chroot() support, but, well, that
didn't go too well. :-) (Actually, it worked fine, but by the time
the kernel options were being parsed, there were already several
threads, meaning only the thread doing option parsing was chroot()'d.
Not quite what I intended...)
Steve
--
Steven Pritchard - K&S Pritchard Enterprises, Inc.
Email: steve@kspei.com http://www.kspei.com/
Phone: (618)398-7360 Mobile: (618)567-7320
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
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:[~2003-12-08 18:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 16:39 [uml-devel] [PATCH] Locking user-mode kernel RAM into host physical RAM Matthew Bloch
2003-12-08 17:31 ` Matt Ayres
2003-12-08 18:02 ` Steven Pritchard [this message]
2003-12-08 18:57 ` [uml-devel] Re: chroot option Henrik Nordstrom
2003-12-08 22:04 ` Jeff Dike
2003-12-08 23:00 ` Henrik Nordstrom
2003-12-08 19:01 ` [uml-devel] [PATCH] Locking user-mode kernel RAM into host physical RAM Jeff Dike
2003-12-08 22:23 ` Matthew Bloch
2003-12-08 23:18 ` Henrik Nordstrom
2003-12-09 0:14 ` Matthew Bloch
2003-12-09 19:00 ` 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=20031208180250.GA7787@osiris.silug.org \
--to=steve@kspei.com \
--cc=matthew-list@bytemark.co.uk \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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.