All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Dumitru <doug@easyco.com>
To: Jeff Dike <jdike@addtoit.com>,
	user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: Patch for buffer overrun in serial/console device logic
Date: Sat, 11 Oct 2003 20:39:01 -0700	[thread overview]
Message-ID: <3F88CCD5.8080508@easyco.com> (raw)
In-Reply-To: <200310110149.h9B1n94f006954@ccure.karaya.com>

Jeff Dike wrote:
> doug@easyco.com said:
> 
>>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. 
> 
> 
> OK, that ain't the way to do it.  Anything that involves passing a parallel
> set of creds through VFS will cause Al Viro to lop my head off.  Since I'm
> somewhat attached to it, I will not propose such a thing, no matter how cleaned
> up it is.

There are actually a couple of sets of issues here.

1.  The "_user" stuff needs to get to UID, GID, and UMASK.

2.  When the "_user" stuff does IO, it should "become" the users in 
UID/GID.  This way permissions "just work" and you don't have to clean 
anything up after the fact.

Addressing (1), I could always just transition a pointer to "current" 
and really open up a can of worms.

This breaks just about every rule of "object orientation", but on the 
other hand, file systems usually do have access to the process state, so 
maybe this is the "correct" approach.

Doing a seteuid(...) ... around the IO calls is actually pretty clean. 
I implemented it with a "change" / "unchange" set of helper routines and 
it pretty much worked first shot.

> What would work is to store the creds in a separate container of some sort
> on the host, and reference that inside hostfs when doing permission checks.
> 
> This is more or less what UMSDOS does, from what I understand, and it keeps
> the nastiness contained within hostfs.
> 
> That journalling is a neat idea, BTW.
> 
> 				Jeff

--------------------------------------------------------------------
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: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2003-10-12  3:36 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
2003-10-11  1:49     ` Jeff Dike
2003-10-12  3:39       ` Doug Dumitru [this message]
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=3F88CCD5.8080508@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 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.