Andrew Kelley e2c741f1e7 std.cache_hash: additionally use file size to detect modifications
I have observed on Linux writing and reading the same file many times
without the mtime changing, despite the file system having nanosecond
granularity (and about 1 millisecond worth of nanoseconds passing between
modifications). I am calling this a Linux Kernel Bug and adding file
size to the cache hash manifest as a mitigation. As evidence, macOS does
not exhibit this behavior.

This means it is possible, on Linux, for a file to be added to the cache
hash, and, if it is updated with the same file size, same inode, within
about 1 millisecond, the cache system will give us a false positive,
saying it is unmodified. I don't see any way to improve this situation
without fixing the bug in the Linux kernel.

closes #6082
2020-08-18 12:44:00 -07:00
..
2020-04-28 19:11:31 -06:00
2020-06-07 22:39:35 +10:00
2020-07-05 21:11:42 +00:00
2020-08-17 13:55:40 -07:00
2020-08-10 17:05:39 -07:00
2020-02-16 13:25:30 -05:00
2019-10-11 18:13:24 -04:00
2020-06-09 13:36:17 -04:00
2020-08-04 23:04:20 -07:00
2020-05-24 10:04:09 -04:00
2020-02-22 12:44:21 +01:00
2020-08-16 22:35:27 -07:00
2020-07-14 17:19:17 -07:00
2020-08-04 23:04:20 -07:00
2020-06-01 14:43:13 -04:00
2020-06-18 20:35:03 -04:00