summaryrefslogtreecommitdiff
path: root/vendor/github.com/vishvananda
diff options
context:
space:
mode:
authorW. Trevor King <wking@tremily.us>2018-07-05 10:57:39 -0700
committerAtomic Bot <atomic-devel@projectatomic.io>2018-07-06 17:54:32 +0000
commitb2344b83ed0bbbd1f8e3ec5efdf09c81ad169941 (patch)
treedfa39cf98c3d4d1e7f651b9e4d062a7f87fd3364 /vendor/github.com/vishvananda
parentaaab26fd0ce812f78ef72b94d921439e7f9d9d6a (diff)
downloadpodman-b2344b83ed0bbbd1f8e3ec5efdf09c81ad169941.tar.gz
podman-b2344b83ed0bbbd1f8e3ec5efdf09c81ad169941.tar.bz2
podman-b2344b83ed0bbbd1f8e3ec5efdf09c81ad169941.zip
pkg/ctime: Factor libpod/finished* into a separate package
This removes some boilerplate from the libpod package, so we can focus on container stuff there. And it gives us a tidy sub-package for focusing on ctime extraction, so we can focus on unit testing and portability of the extraction utility there. For the unsupported implementation, I'm falling back to Go's ModTime [1]. That's obviously not the creation time, but it's likely to be closer than the uninitialized Time structure from cc6f0e85 (more changes to compile darwin, 2018-07-04, #1047). Especially for our use case in libpod/oci, where we're looking at write-once exit files. The test is more complicated than I initially expected, because on Linux filesystem timestamps come from a truncated clock without interpolation [2] (and network filesystems can be completely decoupled [3]). So even for local disks, creation times can be up to a jiffie earlier than 'before'. This test ensures at least monotonicity by creating two files and ensuring the reported creation time for the second is greater than or equal to the reported creation time for the first. It also checks that both creation times are within the window from one second earlier than 'before' through 'after'. That should be enough of a window for local disks, even if the kernel for those systems has an abnormally large jiffie. It might be ok on network filesystems, although it will not be very resilient to network clock lagging behind the local system clock. [1]: https://golang.org/pkg/os/#FileInfo [2]: https://groups.google.com/d/msg/linux.kernel/mdeXx2TBYZA/_4eJEuJoAQAJ Subject: Re: Apparent backward time travel in timestamps on file creation Date: Thu, 30 Mar 2017 20:20:02 +0200 Message-ID: <tqMPU-1Sb-21@gated-at.bofh.it> [3]: https://groups.google.com/d/msg/linux.kernel/mdeXx2TBYZA/cTKj4OBuAQAJ Subject: Re: Apparent backward time travel in timestamps on file creation Date: Thu, 30 Mar 2017 22:10:01 +0200 Message-ID: <tqOyl-36A-1@gated-at.bofh.it> Signed-off-by: W. Trevor King <wking@tremily.us> Closes: #1050 Approved by: mheon
Diffstat (limited to 'vendor/github.com/vishvananda')
0 files changed, 0 insertions, 0 deletions