[CRIU] clock_gettime(MONOTONIC) changing after restore

Cyrill Gorcunov gorcunov at gmail.com
Mon Aug 3 05:53:25 PDT 2015


On Mon, Aug 03, 2015 at 08:31:31AM -0400, Christopher Covington wrote:
> Hi,
> 
> We have notice clock_gettime(MONOTONIC) calls changing significantly across
> checkpoint and restore using CRIU circa 1.3-rc2. We'll be moving to the latest
> tip soon, but I was wondering if anyone knew off the top of their head whether
> we should expect different behavior from a newer CRIU, or if
> clock_gettime(MONOTONIC) (maybe CLOCK_MONOTONIC* and CLOCK_BOOTTIME?) should
> be listed on the following wiki page:
> 
> http://criu.org/What_can_change_after_C/R

Could you provide mode detals please (which values are not adjusted?).
Currently we try to adjust timer's values if they were set to absolute
time (pie/restorer.c:613). This concerns timerfd only. If the problem
in result of clock_gettime syscall itself -- then we indeed do not
intercept this calls neither adjust their results.


More information about the CRIU mailing list