From: David Lang <david@lang.hm>
To: David Howells <dhowells@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
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
Date: Thu, 30 Mar 2017 13:16:24 -0700 (PDT) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1703301315040.3412@qynat-yncgbc> (raw)
In-Reply-To: <23902.1490904827@warthog.procyon.org.uk>
On Thu, 30 Mar 2017, David Howells wrote:
> Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
>> The error bar can be huge, for the simple reason that the filesystem
>> you are testing may not be sharing a clock with the CPU at _all_.
>>
>> IOW, think network filesystems.
>
> Can't I just not do the tests when the filesystem is a network fs? I don't
> think it should be a problem for disk filesystems on network-attached storage.
it's not trivial to detect if a filesystem is local or network (you would have
to do calls to figure out what filesystem you are on, then have a list to define
what's local and what's remote, that list would become out of date as new
filesystems are added)
David Lang
next prev parent reply other threads:[~2017-03-30 20:30 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 [this message]
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
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=nycvar.QRO.7.76.6.1703301315040.3412@qynat-yncgbc \
--to=david@lang.hm \
--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 \
--cc=torvalds@linux-foundation.org \
/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.