Re: fatfs write support

[Marco Gerards]

tb@becket.net (Thomas Bushnell, BSG) writes:

>> In fatfs both the dir ent. and the inode are stored in the same
>> (physical) location.  The problem with the current code is that the
>> same node can be locked twice, once as directory entry and once as
>> inode.
>
> I am inclined to think that one solution here is to change the lock
> structure.
>
> Make the inode lock the *same* as the directory lock.  I think this
> would actually require no changes at all to diskfs.

It already is the same lock, that is causing the problem.  We don't
know if it is locked or not when write_node is called.  I don't see
any change here.

Do you mean that we have to split up the lock and make it more refined?

> In other words, *drop* one lock, rather than adding one.

Unfortunately I don't see how this would solve the problem.  Perhaps
an example (like the diskfs_S_dir_unlink function I have used) will
clear it up.

Thanks,
Marco