On Fri, Apr 11, 2014 at 11:05:30PM +0200, Fabian Frederick wrote: > Ok, that would mean 'older' filesystems -without barrier flag- > to call generic_file_fsync would result in a flush but ext4 without journal > also calls it ; maybe with nobarrier and I'm not sure it's the only case. > How can I deal with this problem ? I don't really think not implementing the barrier option is a problem. For ext4 if you want consistency either opencode generic_file_fsync there and add the check, or add a __generic_file_fsync that doesn't do the flush. -- 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
