From: Jeff Dike <jdike@addtoit.com>
To: Ingo van Lil <inguin@gmx.de>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] hostfs oddities
Date: Thu, 10 Jul 2008 13:37:30 -0400 [thread overview]
Message-ID: <20080710173730.GE18429@c2.user-mode-linux.org> (raw)
In-Reply-To: <48737664.3000608@gmx.de>
On Tue, Jul 08, 2008 at 04:15:00PM +0200, Ingo van Lil wrote:
> The call stack for truncating the file:
>
> - sys_open (fs/open.c)
> - do_sys_open (fs/open.c)
> - do_filp_open (fs/open.c)
> - open_namei (fs/namei.c)
> - may_open (fs/namei.c)
> - do_truncate (fs/open.c)
>
> And the call stack for actually opening the file:
>
> - sys_open (fs/open.c)
> - do_sys_open (fs/open.c)
> - do_filp_open (fs/open.c)
> - nameidata_to_filp (fs/open.c)
> - __dentry_open (fs/open.c)
>
> Maybe that helps.
Yeah, I was suspecting that something was causing operations on the
file before hostfs was asked to actually open it. Hmm.
Jeff
--
Work email - jdike at linux dot intel dot com
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2008-07-10 17:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-05 18:46 [uml-devel] hostfs oddities Ingo van Lil
2008-07-07 20:39 ` Jeff Dike
2008-07-08 14:15 ` Ingo van Lil
2008-07-10 17:37 ` Jeff Dike [this message]
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=20080710173730.GE18429@c2.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=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