linux-um archives
 help / color / mirror / Atom feed
From: Ingo van Lil <inguin@gmx.de>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] hostfs oddities
Date: Sat, 05 Jul 2008 20:46:31 +0200	[thread overview]
Message-ID: <486FC187.6010802@gmx.de> (raw)

Hi there,

I noticed two little misfeatures in the hostfs file system. The first 
one is most certainly a bug, the second one might be functioning as 
intended.

1. If a file is held read-only by one process it cannot by creat()'ed by 
another one:

   [root@localhost ~]# mount -t hostfs none /mnt
   [root@localhost ~]# cd /mnt/tmp
   [root@localhost tmp]# touch foo
   [root@localhost tmp]# tail -f foo &
   [1] 895
   [root@localhost tmp]# > foo
   -bash: foo: Invalid argument
   [root@localhost tmp]# kill 895
   [1]+  Terminated              tail -f foo
   [root@localhost tmp]# > foo

I tracked that problem down to the set_attr() function in hostfs_user.c: 
It tries to ftruncate() the read-only file descriptor. The file should 
be re-opened writable before changing its length.

2. As long as a file is held open changes made outside the UML kernel 
(i.e. on the host side) may not be visible:

   [root@localhost tmp]# tail -f foo &
   [1] 897
   # Host system: echo "Hello World" > /tmp/foo
   [root@localhost tmp]# cat foo
   [root@localhost tmp]# kill 897
   [1]+  Terminated              tail -f foo
   [root@localhost tmp]# cat foo
   Hello World

I guess this is some kind of caching effect, because strace shows that 
there is only a single read to the actual physical file. Maybe hostfs 
should check whether the outside file has changed and invalidate the 
cache if necessary.

Cheers,
Ingo

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
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:[~2008-07-05 18:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-05 18:46 Ingo van Lil [this message]
2008-07-07 20:39 ` [uml-devel] hostfs oddities Jeff Dike
2008-07-08 14:15   ` Ingo van Lil
2008-07-10 17:37     ` Jeff Dike
2008-07-09 19:43   ` Ingo van Lil
2008-07-10 17:28     ` 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=486FC187.6010802@gmx.de \
    --to=inguin@gmx.de \
    --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