linux-kernel - Re: Apparent backward time travel in timestamps on file creation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+55aFz7aAUYoLWS-QZs8LKRL96oozUhu4AtdmPg+az+EuBRyQ@mail.gmail.com>
Date:   Thu, 30 Mar 2017 13:06:11 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     John Stultz <john.stultz@...aro.org>
Cc:     David Howells <dhowells@...hat.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: Apparent backward time travel in timestamps on file creation

On Thu, Mar 30, 2017 at 1:03 PM, John Stultz <john.stultz@...aro.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