Andrew Morton wrote: > That's a bit grubby, because userspace could do > > sync_file_range(SYNC_FILE_RANGE_WAIT_BEFORE); > sync_file_range(SYNC_FILE_RANGE_WRITE); > > expecting it to have the same behaviour as > > sync_file_range(SYNC_FILE_RANGE_WAIT_BEFORE|SYNC_FILE_RANGE_WRITE); Yes it could. The documentation for sync_file_range is unclear enough already. If the distinction is useful, a different SYNC_FILE_RANGE_ flag may be appropriate to indicate write-for-performance vs write-for-integrity, rather than such a peculiar subtlety. -- Jamie -- 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
