From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com ([209.132.183.28]:55486 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934067AbdC3Tfb (ORCPT ); Thu, 30 Mar 2017 15:35:31 -0400 From: David Howells In-Reply-To: References: <22214.1490895007@warthog.procyon.org.uk> To: Linus Torvalds Cc: dhowells@redhat.com, Thomas Gleixner , John Stultz , Linux Kernel Mailing List , linux-fsdevel Subject: Re: Apparent backward time travel in timestamps on file creation MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <23409.1490902528.1@warthog.procyon.org.uk> Date: Thu, 30 Mar 2017 20:35:28 +0100 Message-ID: <23410.1490902528@warthog.procyon.org.uk> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Linus Torvalds wrote: > The difference can be quite noticeable - basically the > "gettimeofday()" time will interpolate within timer ticks, while > "xtime" is just the truncated "time at timer tick" value _without_ the > correction. Is there any way to determine the error bar, do you know? Or do I just make up a fudge factor? Obviously the filesystem truncation would need to be taken into account (and this can be different for different timestamps within the same filesystem). David