From: Jeff Dike <jdike@addtoit.com>
To: BlaisorBlade <blaisorblade_spam@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Werner Almesberger <wa@almesberger.net>
Subject: Re: [uml-devel] uml-patch-2.6.7-2
Date: Wed, 08 Sep 2004 19:15:20 -0400 [thread overview]
Message-ID: <200409082315.i88NFKBP015893@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Sun, 05 Sep 2004 21:35:54 +0200." <200409051844.13906.blaisorblade_spam@yahoo.it>
blaisorblade_spam@yahoo.it said:
> In fact, I'm not able to see the opening with strace (don't ask me why
> - I attach to the kernel thread, but I don't get the opening of the
> file; I got it only once, maybe ), but externfs_lookup calls
> init_inode which calls host_open_file! That's simply brain-damaged!
Maybe, but it's mighty useful in testing the file descriptor reclaiming code.
> - Also (maybe related with calling iget(..., 0) ) I get this message
> on every unmount:
The iget(..., 0) thing has been fixed.
> VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a
> nice day...
I'm not seeing that any more.
> -Finally, for some reasons, the dev and rdev field returned by stat
> are screwed; when listing a device node on hostfs, it prints always
> the maj and min of the device containing the filesystem; i.e., file->
> rdev = host_stat -> dev instead of rdev. And I'm not able to see
> where the exchange happens.
It's here -
copy_stat:
.ust_major = MAJOR(src->st_dev), /* device */
.ust_minor = MINOR(src->st_dev),
do_stat_file:
.rdev = MKDEV(buf.ust_major, buf.ust_minor),
Now that I have externfs_inode_info, either it or uml_stat looks redundant.
One more thing to clean up...
Jeff
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&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 prev parent reply other threads:[~2004-09-08 22:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 3:00 [uml-devel] uml-patch-2.6.7-2 Jeff Dike
2004-08-19 3:00 ` uml-patch-2.6.7-2 Jeff Dike
2004-08-27 7:10 ` [uml-devel] uml-patch-2.6.7-2 Werner Almesberger
2004-09-05 19:35 ` BlaisorBlade
2004-09-08 23:15 ` Jeff Dike [this message]
2004-09-05 15:35 ` BlaisorBlade
2004-09-05 20:28 ` [uml-devel] Current state of UML Jeff Garzik
2004-09-06 17:56 ` BlaisorBlade
2004-09-07 4:40 ` Jeff Garzik
2004-09-07 5:05 ` Adam Heath
2004-09-07 5:13 ` Jeff Garzik
2004-09-07 5:39 ` Adam Heath
2004-09-07 18:13 ` [uml-devel] Current state of UML - some help needed from mainline BlaisorBlade
2004-09-07 18:13 ` BlaisorBlade
2004-09-09 5:30 ` Jeff Garzik
2004-09-09 5:30 ` Jeff Garzik
2004-09-08 20:40 ` [uml-devel] Re: Current state of UML Jeff Dike
2004-09-09 0:35 ` [uml-devel] uml-patch-2.6.7-2 Jeff Dike
2004-09-09 0:35 ` Jeff Dike
2004-09-11 14:41 ` BlaisorBlade
2004-09-11 14:41 ` BlaisorBlade
2004-09-07 21:16 ` [uml-devel] Compiling UML 2.6.8.1 with Static Linking results in segfault Michael Ralston
2004-09-08 0:18 ` Jeff Dike
2004-09-07 23:57 ` Michael Ralston
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=200409082315.i88NFKBP015893@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=blaisorblade_spam@yahoo.it \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=wa@almesberger.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.