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
| ||
|
Date: Thu, 5 Oct 2017 17:54:41 +0200 From: Sebastian Andrzej Siewior <bigeasy@...utronix.de> To: Mike Galbraith <efault@....de> Cc: Thomas Gleixner <tglx@...utronix.de>, LKML <linux-kernel@...r.kernel.org>, linux-rt-users <linux-rt-users@...r.kernel.org>, Steven Rostedt <rostedt@...dmis.org> Subject: Re: [ANNOUNCE] v4.11.12-rt13 On 2017-10-04 18:07:59 [+0200], Mike Galbraith wrote: > Seems combo-patch induced some ltp posix conformance test grumbling. > > +clock_settime_8_1 ... ... FAILED > +clock_settime_4_2 ... ... FAILED > +clock_settime_speculative_4_3 ... ... FAILED > +timer_settime_5_2 ... ... FAILED > +timer_settime_5_1 ... ... FAILED > +timer_settime_5_3 ... ... FAILED > > rtbox:/root # /usr/local/ltp/conformance/interfaces/clock_settime/clock_settime_8-1.run-test > Ended too late. 1507131910 >> 1507131908 > Test FAILED > rtbox:/root # /usr/local/ltp/conformance/interfaces/clock_settime/clock_settime_4-2.run-test > timer should have expired _immediately_ > rtbox:/root # /usr/local/ltp/conformance/interfaces/clock_settime/speculative/clock_settime_speculative_4-3.run-test > Overrun count =0, not # of repeating timer expirys > FAIL: Caught 0 signals, not 1 > Test FAILED > rtbox:/root # /opt/ltp/conformance/interfaces/timer_settime/timer_settime_5-2.run-test > signal was not sent So the last triggers here, too and I have an idea. Sebastian
Powered by blists - more mailing lists