Re: LTP CVE cve-2017-17053 test failed on x86_64 device

2018-06-20 Thread Rafael Tinoco
I believe the error message on boot is solved by LKML thread: [PATCH] locking/rwsem: Fix up_read_non_owner() warning with DEBUG_RWSEMS Looks like that is what is tainting the kernel. On 20 June 2018 at 08:11, Naresh Kamboju wrote: > On 20 June 2018 at 12:51, Michael Moese wrote: >> Hi, >> >> O

Re: LTP CVE cve-2017-17053 test failed on x86_64 device

2018-06-20 Thread Naresh Kamboju
On 20 June 2018 at 12:51, Michael Moese wrote: > Hi, > > On Wed, Jun 20, 2018 at 12:14:22PM +0530, Naresh Kamboju wrote: >> Test FAIL case output, >> tst_test.c:1015: INFO: Timeout per run is 0h 15m 00s >> tst_taint.c:88: BROK: Kernel is already tainted: 512 > The kernel is already tainted. In thi

Re: LTP CVE cve-2017-17053 test failed on x86_64 device

2018-06-20 Thread Michael Moese
Hi, On Wed, Jun 20, 2018 at 12:14:22PM +0530, Naresh Kamboju wrote: > Test FAIL case output, > tst_test.c:1015: INFO: Timeout per run is 0h 15m 00s > tst_taint.c:88: BROK: Kernel is already tainted: 512 The kernel is already tainted. In this case, the test refuses to run, because it could not tell

Re: LTP CVE cve-2017-17053 test failed on x86_64 device

2018-06-20 Thread Jan Stancek
- Original Message - > LTP CVE cve-2017-17053 test failed on x86_64 device. > FAIL on linux-next, mainline, and stable-rc-4.17. > PASS on stable-rc 4.16, 4.14, 4.9 and 4.4 kernel. > > Test FAIL case output, > tst_test.c:1015: INFO: Timeout per run is 0h 15m 00s >

LTP CVE cve-2017-17053 test failed on x86_64 device

2018-06-19 Thread Naresh Kamboju
LTP CVE cve-2017-17053 test failed on x86_64 device. FAIL on linux-next, mainline, and stable-rc-4.17. PASS on stable-rc 4.16, 4.14, 4.9 and 4.4 kernel. Test FAIL case output, tst_test.c:1015: INFO: Timeout per run is 0h 15m 00s tst_taint.c:88: BROK: Kernel is already tainted: 512 Summary: passed