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 <naresh.kamb...@linaro.org> wrote: > On 20 June 2018 at 12:51, Michael Moese <mmo...@suse.de> 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 this case, the test refuses to run, >> because it could not tell if the test is pass or fail. >> >> Could you please check if you could run the test directly after a >> reboot? > > This single test ran immediately after the boot and bug reproduced. > > tst_taint.c:88: BROK: Kernel is already tainted: 512 > https://lkft.validation.linaro.org/scheduler/job/293222#L1204 > > Test command for 10 iterations and it failed for all 10 iterations. > + ./runltp -s cve-2017-17053 -I 10 > > NOTE: > We still see kernel warning while booting the x86_64 machine. > DEBUG_LOCKS_WARN_ON(sem->owner != ((struct task_struct *)(1UL << 0))) > > - Naresh > >> >> Regards, >> Michael >> -- >> SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB >> 21284 (AG Nürnberg)