From: Rob Landley <rob@landley.net>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Hostfs permission checks are all wonky.
Date: Sun, 20 Mar 2005 14:17:59 -0500 [thread overview]
Message-ID: <200503201417.59739.rob@landley.net> (raw)
If I open a device like /dev/loop0 or /dev/console from a hostfs mount, I'll
get the UML device, not the host device, right?
So why are the permissions checks on hostfs devices done relative to the
_host_ user? If /dev/console doesn't belong to the current user, the system
can't even open the initial console, despite the fact the output does NOT go
to TTY1 if I'm running it an xterm.
Similarly, if /dev/loop0 is chmod 600 and I run UML as a normal user and try
to do a mount -o loop, it says it can't find a loop device. Yet if I run UML
as root, it doesn't allocate one of the parent's loop devices, UML does it
internally...
I'm told there's a major rewrite of hostfs underway. Is it worth me trying to
patch the existing hostfs code, or should I go try to track down the new
stuff and try it out?
Rob
-------------------------------------------------------
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&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 reply other threads:[~2005-03-20 23:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-20 19:17 Rob Landley [this message]
2005-03-22 19:19 ` [uml-devel] Hostfs permission checks are all wonky Blaisorblade
2005-03-23 6:09 ` Rob Landley
2005-03-24 10:53 ` Blaisorblade
2005-03-28 17:23 ` Rob Landley
2005-03-28 19:48 ` Rob Landley
2005-04-29 20:53 ` Blaisorblade
2005-04-28 23:45 ` Rob Landley
2005-03-23 8:13 ` Rob Landley
2005-03-24 2:02 ` 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=200503201417.59739.rob@landley.net \
--to=rob@landley.net \
--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.