Re: exofs_file_fsync

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, May 31, 2010 at 01:31:01PM +0300, Boaz Harrosh wrote:
> OK, I was just looking at that. thanks you saved me some digging.
> should I just open-code the generic_file_fsync minus the blocks
> thing then?

sync_mapping_buffers is a no-op for you so you can keep it.
The other difference is that you sync out the superblock at the
end of your fsync implementation.  That is rather unusual, but I don't
know enough about exofs if you really need to update data in the
superblock to commit file data to disk.

> I'm busy with the truncate stuff, but I'll do this next.
> Do you need this ASAP?

I just noticed it while walking through the fsync implementations.

--
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


[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux