linux-kernel - Re: [PATCH 4.13 0/2] 4.13.7-stable review

lists.openwall.net		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 linux-cve-announce 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, 13 Oct 2017 10:00:36 -0700
From:   John Stultz <john.stultz@...aro.org>
To:     Shuah Khan <shuahkh@....samsung.com>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        lkml <linux-kernel@...r.kernel.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Guenter Roeck <linux@...ck-us.net>, patches@...nelci.org,
        Ben Hutchings <ben.hutchings@...ethink.co.uk>,
        stable <stable@...r.kernel.org>
Subject: Re: [PATCH 4.13 0/2] 4.13.7-stable review

On Fri, Oct 13, 2017 at 7:05 AM, Shuah Khan <shuahkh@....samsung.com> wrote:
> On 10/12/2017 06:09 PM, John Stultz wrote:
>> On Thu, Oct 12, 2017 at 4:45 PM, Shuah Khan <shuahkh@....samsung.com> wrote:
>>> On 10/12/2017 03:26 PM, Greg Kroah-Hartman wrote:
>>>> This is the start of the stable review cycle for the 4.13.7 release.
>>>> There are 2 patches in this series, all will be posted as a response
>>>> to this one.  If anyone has any issues with these being applied, please
>>>> let me know.
>>>>
>>>> Responses should be made by Sat Oct 14 21:25:27 UTC 2017.
>>>> Anything received after that time might be too late.
>>>>
>>>> The whole patch series can be found in one patch at:
>>>>       kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.13.7-rc1.gz
>>>> or in the git tree and branch at:
>>>>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.13.y
>>>> and the diffstat can be found below.
>>>>
>>>
>>> Compiled and booted on my test system. No dmesg regressions.
>>> kselftest run regression since 4.13.6
>>>
>>> selftests: posix_timers
>>>
>>> selftests: raw_skew
>>> ========================================
>>> not ok 1..7 selftests:  raw_skew [FAIL]
>>
>> Hrm... Did raw_skew provide any other output?
>>
>> Also, did you turn ntpd off before running?
>>
>> -john
>>
>
> John/Greg,
>
> Here is the detailed report fromn this test. I didn't disable ntpd.
>
> WARNING: ADJ_OFFSET in progress, this will cause inaccurate results

So this warning means someone is adjusting the clock while the test is running.
Can you insure you are running the test with ntpd/chrony(/whatever
systemd's time sync is) turned off?

thanks
-john