From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
To: Adam Heath <adam@doogie.org>
Cc: Matt Zimmerman <mdz@debian.org>,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] hostfs as root
Date: Fri, 05 Sep 2003 12:28:56 -0400 [thread overview]
Message-ID: <11075.1062779336@marajade.sandelman.ottawa.on.ca> (raw)
In-Reply-To: Your message of "Fri, 05 Sep 2003 11:06:43 CDT." <Pine.LNX.4.44.0309051106050.686-100000@gradall.private.brainfood.com>
-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "Adam" == Adam Heath <adam@doogie.org> writes:
Adam> On Fri, 5 Sep 2003, Michael Richardson wrote:
>> >> I propose: stat(), save permissions chmod(u+rw) (as appropriate for
>> >> the open) open() chmod(oldperms)
>>
Matt> Sounds like a recipe for lots of race conditions.
>> Uh, how? Remember, this is in the kernel. We have locks.
>>
>> If two UMLs come along, using the same rootfs, well, that's a
>> different problem.
Adam> No, it's a problem. Just because there's no race in the emulated
Adam> environment, doesn't mean there isn't a race in the host.
I don't think that hostfs provides any inter-UML locking guarantees.
What do we do with flock(2)?
If you like, we can flock(2) the file too while we play with it.
] 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
iQCVAwUBP1i5x4qHRg3pndX9AQErKAQAjb02jUIC6x+RT3ojY8Ta9G3wuyqJFs35
O/ySSn/73X5kaAc3Vh96zSkaLI3+hE3LTR+CWhtbfSGFZCXDjcahVu9/2wuUm8Ud
7p6/1C7ZwNOZk5EJk/8rGpHP2oJAl4qY/bvcSoZ9f1JequzCilhjyxuua/4t09kW
ZxqtZdP9nEM=
=TF2P
-----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 16:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0309020854560.26729-100000@filer.marasystems.com>
2003-09-02 16:28 ` [uml-devel] hostfs as root 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 [this message]
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
2003-09-05 15:14 stian
2003-09-05 17:58 ` Michael Richardson
2003-09-05 18:19 ` Matt Zimmerman
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=11075.1062779336@marajade.sandelman.ottawa.on.ca \
--to=mcr@sandelman.ottawa.on.ca \
--cc=adam@doogie.org \
--cc=mdz@debian.org \
--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