On Tue, Dec 02, 2014 at 01:37:27PM -0700, Andreas Dilger wrote: > > One thing that comes to mind is touch/utimes()/utimensat(). Those > should definitely not result in timestamps being kept only in memory > for 24h, since the whole point of those calls is to update the times. > It makes sense for these APIs to dirty the inode for proper writeout. Not a problem. Touch/utimes* go through notify_change() and ->setattr, so they won't go through the I_DIRTY_TIME code path. - Ted -- 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
