From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751997AbeAYMZR (ORCPT <rfc822;w@1wt.eu>);
        Thu, 25 Jan 2018 07:25:17 -0500
Received: from mx2.suse.de ([195.135.220.15]:40002 "EHLO mx2.suse.de"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1751567AbeAYMZQ (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 25 Jan 2018 07:25:16 -0500
Date: Thu, 25 Jan 2018 13:24:59 +0100
From: Cyril Hrubis <chrubis@suse.cz>
To: Juri Lelli <juri.lelli@redhat.com>
Cc: kernel test robot <xiaolong.ye@intel.com>,
        Stephen Rothwell <sfr@canb.auug.org.au>,
        Juri Lelli <juri.lelli@arm.com>, Peter Zijlstra <peterz@infradead.org>,
        Viresh Kumar <viresh.kumar@linaro.org>,
        Luca Abeni <luca.abeni@santannapisa.it>,
        "Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
        LKML <linux-kernel@vger.kernel.org>,
        Claudio Scordino <claudio@evidence.eu.com>, lkp@01.org,
        Thomas Gleixner <tglx@linutronix.de>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Ingo Molnar <mingo@kernel.org>, ltp@lists.linux.it
Subject: Re: [LTP] [lkp-robot] [sched/deadline] e0367b1267:
 WARNING:at_kernel/sched/sched.h:#assert_clock_updated
Message-ID: <20180125122458.GB3420@rei>
References: <20180125062839.GM5185@yexl-desktop>
 <20180125112013.GA6110@localhost.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20180125112013.GA6110@localhost.localdomain>
User-Agent: Mutt/1.7.2 (2016-11-26)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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

-- 
Cyril Hrubis
chrubis@suse.cz

From mboxrd@z Thu Jan  1 00:00:00 1970
From: Cyril Hrubis <chrubis@suse.cz>
Date: Thu, 25 Jan 2018 13:24:59 +0100
Subject: [LTP] [lkp-robot] [sched/deadline] e0367b1267:
 WARNING:at_kernel/sched/sched.h:#assert_clock_updated
In-Reply-To: <20180125112013.GA6110@localhost.localdomain>
References: <20180125062839.GM5185@yexl-desktop>
 <20180125112013.GA6110@localhost.localdomain>
Message-ID: <20180125122458.GB3420@rei>
List-Id: <ltp.lists.linux.it>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: ltp@lists.linux.it

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

-- 
Cyril Hrubis
chrubis@suse.cz

From mboxrd@z Thu Jan  1 00:00:00 1970
Content-Type: multipart/mixed; boundary="===============7698846649655481857=="
MIME-Version: 1.0
From: Cyril Hrubis <chrubis@suse.cz>
To: lkp@lists.01.org
Subject: Re: [LTP] [lkp-robot] [sched/deadline] e0367b1267: WARNING:at_kernel/sched/sched.h:#assert_clock_updated
Date: Thu, 25 Jan 2018 13:24:59 +0100
Message-ID: <20180125122458.GB3420@rei>
In-Reply-To: <20180125112013.GA6110@localhost.localdomain>
List-Id: <oe-lkp.lists.linux.dev>

--===============7698846649655481857==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

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

-- =

Cyril Hrubis
chrubis(a)suse.cz

--===============7698846649655481857==--