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  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]
Date:   Fri, 27 Apr 2018 09:41:30 +0200
From:   Miroslav Lichvar <>
To:     Jeffrin Thalakkottoor <>
Cc:     Thomas Gleixner <>,,
        Kees Cook <>,,, Tony Luck <>,
        John Stultz <>,,,
        LKML <>
Subject: Re: possible BUG: selftest about raw_skew failed

On Thu, Apr 26, 2018 at 11:28:29PM +0200, Thomas Gleixner wrote:
> On Sat, 21 Apr 2018, Jeffrin Thalakkottoor wrote:
> > selftests: raw_skew
> > ========================================
> > WARNING: ADJ_OFFSET in progress, this will cause inaccurate results
> > Estimating clock drift: 17.910(est) 16.820(act) [FAILED]

Was ntpd, systemd-timesyncd, or some other NTP/PTP daemon running
shortly before or during the test?

The warning indicates that the clock was slewed by adjtime() or
adjtimex(), which makes the measurement of the frequency less accurate
and the test may fail.

Maybe this test and other tests that measure the frequency of the
system clock should be modified to SKIP when adjtimex() returns a
non-zero offset (or the frequency changes during the test)? 

Miroslav Lichvar

Powered by blists - more mailing lists