From: Doug Dumitru <doug@easyco.com>
To: Jeff Dike <jdike@addtoit.com>,
user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: Patch for buffer overrun in serial/console device logic
Date: Tue, 07 Oct 2003 15:31:08 -0700 [thread overview]
Message-ID: <3F833EAC.20903@easyco.com> (raw)
In-Reply-To: <200310072151.h97LphCt003529@ccure.karaya.com>
Jeff Dike wrote:
> doug@easyco.com said:
>
>>We also have a much messier, in-house patch that we apply to hostfs.c
>>so that root mounts will correctly honor ownerships and rights.
>
>
> Does this involve some sort of list on the side which keeps track of ownership
> and permissions of the host files? If so, hostfs has needed something like
> this for a long time.
>
>
>>Is anyone else working on this.
>
>
> Not that I know of. It comes up every once in a while, but no one has actually
> written any code.
>
> Jeff
The in-house patch that we are running assumes that you boot UML as
root, although I have considered a SUID root variant.
It looks at numeric UID/GIDs and maintains all of these all the way down
to the user IO calls. Thus the files created in the hostfs have
parellel UID/GID values and priviledges.
The code itself involves a lot of extra parameters from kernel to user
space as things like the current user aren't propogated down. I
personally think that our current patch set is "100% ugly" and would not
consider posting it as-is. If people are interested in transparent
numeric UID/GID to hostfs, then I would be happy to clean up what we
have and submit it.
Our reason for doing the patch in-house is that we have added UML kernel
code that supports an in-house application that causes hostfs to keep a
"journel" of file IO transactions and posts this journel to a host pipe.
We then have host daemons (outside of the virtual) that move this
journel to a distant machine achieving remote filesystem replication.
We use this for high-reliability mail and web services.
--------------------------------------------------------------------
Doug Dumitru 800-470-2756 (610-237-2000)
EasyCo LLC doug@easyco.com http://easyco.com
--------------------------------------------------------------------
D3, U2, jBase Virtual Servers. Off-site backup over the internet.
Develop/test/deploy from $20/mo. Fast, secure, cheaper than tape.
http://mirroredservers.com http://mirroredbackup.com
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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-10-07 22:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 18:55 [uml-devel] Patch for buffer overrun in serial/console device logic Doug Dumitru
2003-10-07 21:51 ` [uml-devel] " Jeff Dike
2003-10-07 22:31 ` Doug Dumitru [this message]
2003-10-11 1:49 ` Jeff Dike
2003-10-12 3:39 ` Doug Dumitru
2003-10-13 20:43 ` BlaisorBlade
[not found] ` <p05111b00bba97b88a68d@[10.96.96.13]>
2003-10-08 16:25 ` [uml-devel] " Doug Dumitru
2003-11-09 1:53 ` [uml-devel] " 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=3F833EAC.20903@easyco.com \
--to=doug@easyco.com \
--cc=jdike@addtoit.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox