DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 03AC87F748
Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley
        Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United
        Kingdom.
        Registered in England and Wales under Company Registration No. 3798903
From: David Howells <dhowells@redhat.com>
In-Reply-To: <CA+55aFzcMjJsrtwGDb3NOWC=Ubrv=BuDx3nU-eMBJiRM1hRafA@mail.gmail.com>
References: <CA+55aFzcMjJsrtwGDb3NOWC=Ubrv=BuDx3nU-eMBJiRM1hRafA@mail.gmail.com> <22214.1490895007@warthog.procyon.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dhowells@redhat.com, Thomas Gleixner <tglx@linutronix.de>,
        John Stultz <john.stultz@linaro.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        linux-fsdevel <linux-fsdevel@vger.kernel.org>
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-kernel-owner@vger.kernel.org
Content-Length: 524
Lines: 14

Linus Torvalds <torvalds@linux-foundation.org> 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