From mboxrd@z Thu Jan 1 00:00:00 1970 From: Juri Lelli Date: Thu, 25 Jan 2018 14:29:06 +0100 Subject: [LTP] [lkp-robot] [sched/deadline] e0367b1267: WARNING:at_kernel/sched/sched.h:#assert_clock_updated In-Reply-To: <20180125122458.GB3420@rei> References: <20180125062839.GM5185@yexl-desktop> <20180125112013.GA6110@localhost.localdomain> <20180125122458.GB3420@rei> Message-ID: <20180125132906.GA10968@localhost.localdomain> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ltp@lists.linux.it On 25/01/18 13:24, Cyril Hrubis wrote: > 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. Thanks for pointing this out. Best, - Juri From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============4271925049616114247==" MIME-Version: 1.0 From: Juri Lelli 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 14:29:06 +0100 Message-ID: <20180125132906.GA10968@localhost.localdomain> In-Reply-To: <20180125122458.GB3420@rei> List-Id: --===============4271925049616114247== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On 25/01/18 13:24, Cyril Hrubis wrote: > 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. Thanks for pointing this out. Best, - Juri --===============4271925049616114247==-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751372AbeAYN3Y (ORCPT ); Thu, 25 Jan 2018 08:29:24 -0500 Received: from mail-wr0-f195.google.com ([209.85.128.195]:34441 "EHLO mail-wr0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751334AbeAYN3L (ORCPT ); Thu, 25 Jan 2018 08:29:11 -0500 X-Google-Smtp-Source: AH8x226VLESwE1AOgBccrjiGwPOTrQQ9vcYckEhVUnOzF6hV+inEeQUZL/zwn0HsbWSj6bd+azxHjQ== Date: Thu, 25 Jan 2018 14:29:06 +0100 From: Juri Lelli To: Cyril Hrubis Cc: kernel test robot , Stephen Rothwell , Juri Lelli , Peter Zijlstra , Viresh Kumar , Luca Abeni , "Rafael J . Wysocki" , LKML , Claudio Scordino , lkp@01.org, Thomas Gleixner , Linus Torvalds , Ingo Molnar , ltp@lists.linux.it Subject: Re: [LTP] [lkp-robot] [sched/deadline] e0367b1267: WARNING:at_kernel/sched/sched.h:#assert_clock_updated Message-ID: <20180125132906.GA10968@localhost.localdomain> References: <20180125062839.GM5185@yexl-desktop> <20180125112013.GA6110@localhost.localdomain> <20180125122458.GB3420@rei> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180125122458.GB3420@rei> User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 25/01/18 13:24, Cyril Hrubis wrote: > 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. Thanks for pointing this out. Best, - Juri