linux-kernel - Re: LTS testing with latest kselftests

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]

Message-ID: <20170616235548.3uiqrhnrjrfw4gx3@wfg-t540p.sh.intel.com>
Date:   Sat, 17 Jun 2017 07:55:48 +0800
From:   Fengguang Wu <fengguang.wu@...el.com>
To:     "Luis R. Rodriguez" <mcgrof@...nel.org>
Cc:     Sumit Semwal <sumit.semwal@...aro.org>,
        Brian Norris <computersforpeace@...il.com>,
        Kees Cook <keescook@...omium.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        shuah@...nel.org, LKML <linux-kernel@...r.kernel.org>,
        stable@...r.kernel.org, linux-kselftest@...r.kernel.org,
        Martin Fuzzey <mfuzzey@...keon.com>,
        Alan Cox <alan@...ux.intel.com>
Subject: Re: LTS testing with latest kselftests - some failures

On Fri, Jun 16, 2017 at 06:46:51PM +0200, Luis R. Rodriguez wrote:
>Kees, please review 47e0bbb7fa98 below.
>Brian, please review be4a1326d12c below.
>
>On Thu, Jun 15, 2017 at 11:26:53PM +0530, Sumit Semwal wrote:
>> Hello Greg, Shuah,
>>
>> While testing 4.4.y and 4.9.y LTS kernels with latest kselftest,
>
>To be clear it seems like you are taking the latest upstream ksefltest and run
>it against older stable kernels. Furthermore you seem to only run the shell
>script tests but are using older kselftests drivers? Is this all correct?
>Otherwise it is unclear how you are running into the issues below.
>
>Does 0-day so the same? I thought 0-day takes just the kselftest from each tree
>submitted. That *seemed* to me like the way it was designed. Shuah ?

Yes in 0-day, we run the kselftest code corresponding to the current kernel.

Thanks,
Fengguang