From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
To: stian@nixia.no
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] hostfs as root
Date: Fri, 05 Sep 2003 13:58:35 -0400 [thread overview]
Message-ID: <28537.1062784715@marajade.sandelman.ottawa.on.ca> (raw)
In-Reply-To: Your message of "Fri, 05 Sep 2003 17:14:57 +0200." <19654.193.212.97.12.1062774897.squirrel@pluto.nixia.no>
-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "stian" == stian <stian@nixia.no> writes:
stian> The problem occurs when you create a file you are later not
stian> allowed to
stian> open if I'm seeing this right, so, the best fix would be not to
stian> close the
stian> file when we create them in the first place. Fix the behavour that
stian> we
I believe that we do this because in TT mode at least, we may have to open
it in multiple processes.
So the fix would work for SKAS, but not TT mode.
stian> The mode issue goes pretty much away, since trying to open a file
stian> you are not allowed to read will normally fail both in host and
stian> uml. Only problem is when creating new files as far as I can see.
Root can open a file for write that doesn't have write permissions.
] Out and about in Ottawa. hmmm... beer. | firewalls [
] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
] panic("Just another Debian/notebook using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Finger me for keys - custom hacks make this fully PGP2 compat
iQCVAwUBP1jOyoqHRg3pndX9AQG4cAP/codBpW4FkhBKFrLpDmFpp5+tqy0hPVlt
VFwfdJ3nTKJzWJBkt82FVH9J5/2MkVTN0w+V4/LWw/DskOz22YdIczyoFZIXTChK
IGHncjsx8FMhhgxwBZ8s9toHluQGG8t88ZRETDLQQmm3BIBGfUmlsVUdoLRjKhvg
dyi7xT4sT3s=
=mfEh
-----END PGP SIGNATURE-----
-------------------------------------------------------
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-09-05 17:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-05 15:14 [uml-devel] hostfs as root stian
2003-09-05 17:58 ` Michael Richardson [this message]
2003-09-05 18:19 ` Matt Zimmerman
[not found] <Pine.LNX.4.44.0309020854560.26729-100000@filer.marasystems.com>
2003-09-02 16:28 ` Michael Richardson
2003-09-03 9:32 ` Henrik Nordstrom
2003-09-03 15:47 ` Matt Zimmerman
2003-09-03 18:22 ` Michael Richardson
2003-09-03 18:55 ` Henrik Nordstrom
2003-09-03 19:16 ` Matt Zimmerman
2003-09-05 0:55 ` Michael Richardson
2003-09-05 1:10 ` Matt Zimmerman
2003-09-05 13:43 ` Michael Richardson
2003-09-05 14:01 ` Matt Zimmerman
2003-09-05 15:50 ` Michael Richardson
2003-09-05 16:06 ` Adam Heath
2003-09-05 16:28 ` Michael Richardson
2003-09-05 16:44 ` Adam Heath
2003-09-05 16:13 ` Matt Zimmerman
2003-09-05 17:37 ` Michael Richardson
2003-09-05 18:02 ` Matt Zimmerman
2003-09-05 18:39 ` Michael Richardson
2003-09-05 18:49 ` Matt Zimmerman
2003-09-17 16:43 ` 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=28537.1062784715@marajade.sandelman.ottawa.on.ca \
--to=mcr@sandelman.ottawa.on.ca \
--cc=stian@nixia.no \
--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