On Mon, Sep 21, 2009 at 01:15:19PM -0700, Andrew Morton wrote: > The syscall is all about dirty memory management and userspace control > over IO timing/volume. Trying to use it for data integrity purposes is a > bit perverse. Yes, its is. But that needs to be clearly documented. If you have better wording to make it crystal clear you're welcome. Additionally I have a half-backed patch to allow it calling into ->fsync to actually make it usable as a fdatasync_range/fsync_range, but I wonder if we should just add those as syscalls instead. -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
