On Wed, 4 Jan 2017 18:24:39 +0100 Vitaly Kuznetsov <vkuznets@xxxxxxxxxx> wrote: > If we happen to receive interrupts during hv_set_host_time() execution > our adjustments may get inaccurate. Make the whole function atomic. > Unfortunately, we can's call do_settimeofday64() with interrupts > disabled as some cross-CPU work is being done but this call happens > very rarely. > > Signed-off-by: Vitaly Kuznetsov <vkuznets@xxxxxxxxxx> Ok, the race is between timer interrupts and calling do_adjtimex(). NTP has the same issue already. The getnstimeofday64() (or ktime_get) return an atomic value. If a clock tick interrupt happens during this code, then the value is still correct just old. If you want to avoid all races here, it looks like it would be better to get timekeeper_lock and call __do_adjtimex. The existing code in do_adjtimex() is expecting to be called from a system call and changing it's assumptions is probably not a good idea. Rather than calling system call from user space. Maybe better to provide real kernel API in time subsystem for this use case. What does KVM do? _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
