On Wed, Dec 04, 2002 at 08:45:46PM +0100, M. Gerards wrote: > > > > There are still two locking problems. I'm working on those problems ATM. > > > Because of those problems fatfs will most likely freeze while testing it. > > > > Even in read-only mode? My understanding was that the locking problems only > > occur when writing. Certainly the fatfs I wrote (0.2) worked fine in read > > only mode. > > No, it didn't. And if you are really sure, please tell me what I did wrong ;). > > The problem is in read_node. It calls diskfs_cached_lookup to look up the > directory holding the node because the stat information (inode) is stored in the > directory. The directory needs to be locked, but is already locked in some cases.
Ah, right. D'oh. > There is another locking problem triggered by writing support, I assume you were > thinking about that one... Yow, there are more than I remembered. > I thought I already explained this serveral times... Yeah, but my mind is a sieve ;) I will put down everything that needs to be done in the Savannah task system. Thanks, Marcus -- `Rhubarb is no Egyptian god.' GNU http://www.gnu.org [EMAIL PROTECTED] Marcus Brinkmann The Hurd http://www.gnu.org/software/hurd/ [EMAIL PROTECTED] http://www.marcus-brinkmann.de/ _______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd
