On Thu, Dec 06, 2018 at 10:10:11AM -0200, Rafael David Tinoco wrote:
On 12/6/18 8:05 AM, Linaro QA (BETA) wrote:
Summary
kernel: 4.20.0-rc5 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git git branch: master git commit: 4eaaa2b99e30305f4bc677f4abfe56c1f8b39670 git describe: v4.20-rc5-47-g4eaaa2b99e30 Test details: https://qa-reports.linaro.org/lkft/linux-mainline-oe/build/v4.20-rc5-47-g4ea...
Regressions (compared to build v4.20-rc5-44-gd08970904582)
qemu_i386: ltp-cve-tests: * cve-2017-17053
This is failing for i386 in all tests.
i386
...
- spectre-meltdown-checker-test - fail: 5, pass: 3,
Are we testing the CVEs together with spectre-meltdown-checker-test already ?
We will have to check spectre-meltdown-checker-test results every time there is a cve-XXXX-XXXXX (related to either meltdown or spectre) test failure.. in order to know if it was a false positive.
The way I'm reading this, those:
CVE-2017-5753: OK CVE-2017-5715: OK CVE-2017-5754: VULN CVE-2018-3640: VULN CVE-2018-3639: VULN CVE-2018-3615: VULN CVE-2018-3620: VULN CVE-2018-3646: OK
are only coming from spectre-meltdown-checker, right ?
Like here:
https://qa-reports.linaro.org/lkft/linux-mainline-oe/build/v4.20-rc5-47-g4ea...
I thought we would run spectre-meltdown-checker simultaneously with ltp-cve-tests.. Are we splitting the ltp-cve-tests into ltp-cve-tests and ltp-cve-tests + spectre-meltdown-checker (this last having only spectre and meltdown cve related tests) ?
Did I miss something ?
ltp-cve-tests and spectre-meltdown-checker run in the same lava job (for example https://lkft.validation.linaro.org/scheduler/job/537010 to use your example), but they report as separate test suites in qa-reports.
Does that help?
Thanks!
-- Rafael D. Tinoco Linaro - Kernel Validation