Received: by 10.223.176.46 with SMTP id f43csp2139926wra; Thu, 25 Jan 2018 05:37:39 -0800 (PST) X-Google-Smtp-Source: AH8x227SZUVJDyvEI+QPO6kIo+Y9AP2DVEZ772vcEv5G1JrR6YnAFMHaK2HjlOy3QL+n9ZCJOkMZ X-Received: by 2002:a17:902:781:: with SMTP id 1-v6mr11192063plj.411.1516887459095; Thu, 25 Jan 2018 05:37:39 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516887459; cv=none; d=google.com; s=arc-20160816; b=MnI8ba5hXjELD/+jA5sx4pcf2q1gY4dZcHqx1oY3wTWqqmtc7XgtB0QIUp+3zTk3k5 oA5YqwFHGnXnmRt0Ck30h9gfdAW5/eeugV4J4yvkKjnFT2u5cyfTAmeirw8ds0wY/3BF GO/ZkXCjopvVhTHsiGJYwSJTY0IaXNPMcVjrsgX9eqOXbJOCwaVx0/z64LpRAu3brN9K 3ZH5uEXTXH4+RsYbWsVoQcZ6IcY7xQT7gFfjyZblS0q06KOrOmU0QpVIBdyhjYQo+v0m PrtOCUCffbh+YuDSoP/Qv24CaD+FWXPzfuZ0XxaGH2WZHhnEM3UVNzp8YKCVPbbH65xJ +NUQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=Wp67EmBDghQ+Z2NrYMi1TwBctU5eyLjT9GAzysri3j0=; b=EhxbBrMtDVcZVn7JIGCXW3I0vekjoAGY4kwLx3xAPh6KzGNCODSuYIyyT/meUkl4g0 sS/LqEOXnrWF7zXmYdyfxPIZc/GrS9AoQpvNB/nypVuzBppJutBen1aDJ/GWBaVKe0h4 HaCYyCt2A+CR/aYn9Q3y1ZUdJ+zm5vfQ+fXxGvqUCZS09a5ocDc6xu9us+kdnH8D0Hp1 yHl5a9zmH4o/so7QWN1oRa3XJZ58s8/6a2CgHDgU28dQmAP9q6VePoba5gRNMSfnRBDt T2hl5K3ZIgl0qmcJpiadmTKH8CnV0g9wtpdhClCXIa9M/DF9whY8amdLFyqBQlHVVO1l 6sTQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c21si1585900pgn.225.2018.01.25.05.37.24; Thu, 25 Jan 2018 05:37:39 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751250AbeAYNgJ (ORCPT + 99 others); Thu, 25 Jan 2018 08:36:09 -0500 Received: from mx2.suse.de ([195.135.220.15]:45394 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751011AbeAYNgI (ORCPT ); Thu, 25 Jan 2018 08:36:08 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay1.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 946F5ADE2; Thu, 25 Jan 2018 13:36:06 +0000 (UTC) Date: Thu, 25 Jan 2018 14:35:51 +0100 From: Cyril Hrubis To: Juri Lelli 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: <20180125133551.GB19878@rei.lan> References: <20180125062839.GM5185@yexl-desktop> <20180125112013.GA6110@localhost.localdomain> <20180125122458.GB3420@rei> <20180125132906.GA10968@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180125132906.GA10968@localhost.localdomain> User-Agent: Mutt/1.7.2 (2016-11-26) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: 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 > > 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@suse.cz