On 06/01/2010 01:04 PM, Christoph Hellwig wrote: > > The pages are written by vfs_fsync_range. You need to make sure > that the inode back, or if the datasync flag is set only changes > to the inode require to find that data are written back. That's > basically a messy wording for you can skip dirtiness of timestamp > updates if the datasync flag is set. > > Note that your patch below is very wrong for this, as it does > a lot of asynchronous activity if the datasync flag is not set. > Thank you Christoph. Me smack me on the head. Got two unrelated flags totally confused. I'll be posting a fix. For the best of my knowledge all I need is a synchronous call to sync_inode() which will in turn call exofs_write_inode. The later takes care of all metadata an exofs inode has. (No allocation bitmaps, no data nodes lists, etc...) In a next patch I'll also fix the super-block shit. Testing ... Boaz -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
