If atime has been wrong set to future, then it cannot be updated back to current time. CC: swhiteho@xxxxxxxxxx Signed-off-by: sickadm@xxxxxxxxx Reviewed-by: adilger@xxxxxxxxx --- fs/inode.c | 12 ++++++++++-- 1 files changed, 10 insertions(+), 2 deletions(-) diff --git a/fs/inode.c b/fs/inode.c index da85e56..9cf7375 100644 --- a/fs/inode.c +++ b/fs/inode.c @@ -1446,6 +1446,8 @@ sector_t bmap(struct inode *inode, sector_t block) } EXPORT_SYMBOL(bmap); +#define RELATIME_MARGIN (24 * 60 * 60) + /* * With relative atime, only update atime if the previous atime is * earlier than either the ctime or mtime or if at least a day has @@ -1469,10 +1471,16 @@ static int relatime_need_update(struct vfsmount *mnt, struct inode *inode, return 1; /* - * Is the previous atime value older than a day? If yes, + * Is the previous atime value in future? If yes, + * update atime: + */ + if ((long)(now.tv_sec - inode->i_atime.tv_sec) < -RELATIME_MARGIN) + return 1; + /* + * Is the previous atime value old than a day? If yes, * update atime: */ - if ((long)(now.tv_sec - inode->i_atime.tv_sec) >= 24*60*60) + if ((long)(now.tv_sec - inode->i_atime.tv_sec) >= RELATIME_MARGIN) return 1; /* * Good, we can skip the atime update: -- 1.7.2.3 -- 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
