Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S934926AbdC3UGQ (ORCPT <rfc822;w@1wt.eu>);
        Thu, 30 Mar 2017 16:06:16 -0400
Received: from mail-io0-f178.google.com ([209.85.223.178]:33209 "EHLO
        mail-io0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S933493AbdC3UGN (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 30 Mar 2017 16:06:13 -0400
MIME-Version: 1.0
In-Reply-To: <CALAqxLWR0g1dEOO0kMtpDL9grmKxTVx7ELhsW6055saQi+F1HA@mail.gmail.com>
References: <22214.1490895007@warthog.procyon.org.uk> <CA+55aFzcMjJsrtwGDb3NOWC=Ubrv=BuDx3nU-eMBJiRM1hRafA@mail.gmail.com>
 <23410.1490902528@warthog.procyon.org.uk> <CALAqxLWR0g1dEOO0kMtpDL9grmKxTVx7ELhsW6055saQi+F1HA@mail.gmail.com>
From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Thu, 30 Mar 2017 13:06:11 -0700
X-Google-Sender-Auth: 5WY3XgFlhJ4XdmdER4BnisW_ZtQ
Message-ID: <CA+55aFz7aAUYoLWS-QZs8LKRL96oozUhu4AtdmPg+az+EuBRyQ@mail.gmail.com>
Subject: Re: Apparent backward time travel in timestamps on file creation
To: John Stultz <john.stultz@linaro.org>
Cc: David Howells <dhowells@redhat.com>,
        Thomas Gleixner <tglx@linutronix.de>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        linux-fsdevel <linux-fsdevel@vger.kernel.org>
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 414
Lines: 12

On Thu, Mar 30, 2017 at 1:03 PM, John Stultz <john.stultz@linaro.org> wrote:
>
> Again, I'd utilize clock_gettime(CLOCK_REALTIME_COARSE, ...) for this
> instead of playing with fudge factors.

See my note on network filesystems. It won't help.

fudgefactors would at least work. Allow people to set them large for
filesystems with low granularity, or networks with bad time
synchronization.

                Linus