All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
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>
Subject: Re: Apparent backward time travel in timestamps on file creation
Date: Thu, 30 Mar 2017 13:06:11 -0700	[thread overview]
Message-ID: <CA+55aFz7aAUYoLWS-QZs8LKRL96oozUhu4AtdmPg+az+EuBRyQ@mail.gmail.com> (raw)
In-Reply-To: <CALAqxLWR0g1dEOO0kMtpDL9grmKxTVx7ELhsW6055saQi+F1HA@mail.gmail.com>

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

      reply	other threads:[~2017-03-30 20:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-30 17:30 Apparent backward time travel in timestamps on file creation David Howells
2017-03-30 18:07 ` Linus Torvalds
2017-03-30 18:49 ` John Stultz
2017-03-30 19:35 ` David Howells
2017-03-30 19:52   ` Linus Torvalds
2017-03-30 20:04     ` Linus Torvalds
2017-03-30 20:13     ` David Howells
2017-03-30 20:16       ` David Lang
2017-03-30 21:13       ` Linus Torvalds
2017-03-31 12:35         ` Bob Peterson
2017-03-30 22:22       ` David Howells
2017-03-30 20:03   ` John Stultz
2017-03-30 20:06     ` Linus Torvalds [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA+55aFz7aAUYoLWS-QZs8LKRL96oozUhu4AtdmPg+az+EuBRyQ@mail.gmail.com \
    --to=torvalds@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=john.stultz@linaro.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.