linux-kernel - Re: [LTP] [lkp-robot] [sched/deadline] e0367b1267: WARNING:at_kernel/sched/sched.h:#assert_clock

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] [day] [month] [year] [list]

Message-ID: <20180125133551.GB19878@rei.lan>
Date:   Thu, 25 Jan 2018 14:35:51 +0100
From:   Cyril Hrubis <chrubis@...e.cz>
To:     Juri Lelli <juri.lelli@...hat.com>
Cc:     kernel test robot <xiaolong.ye@...el.com>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Juri Lelli <juri.lelli@....com>,
        Peter Zijlstra <peterz@...radead.org>,
        Viresh Kumar <viresh.kumar@...aro.org>,
        Luca Abeni <luca.abeni@...tannapisa.it>,
        "Rafael J . Wysocki" <rafael.j.wysocki@...el.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Claudio Scordino <claudio@...dence.eu.com>, lkp@...org,
        Thomas Gleixner <tglx@...utronix.de>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Ingo Molnar <mingo@...nel.org>, ltp@...ts.linux.it
Subject: Re: [LTP] [lkp-robot] [sched/deadline] e0367b1267:
 WARNING:at_kernel/sched/sched.h:#assert_clock_updated

Hi!
> > > Hummm, wondering how LTP sched tests could trigger this, since a quick
> > > grep into ltp didn't show DEADLINE usage.
> > 
> > See kernel/syscalls/sched_setattr/sched_setattr01.c
> 
> Right, saw that. I was still thinking though why the report seemed to
> point to sched, and not syscalls, tests.

These collections of tests have sometimes non empty intersections. In
this case the particular test is both part of the sched and syscall
testruns (grep sched_setattr01 runtest/*). So I suppose that the test
fails both in the sched and syscall run but the sched one was simply
picked first here.

> Thanks for pointing this out.

Glad to help :-).

-- 
Cyril Hrubis
chrubis@...e.cz