All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juri Lelli <juri.lelli@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [lkp-robot] [sched/deadline] e0367b1267: WARNING:at_kernel/sched/sched.h:#assert_clock_updated
Date: Thu, 25 Jan 2018 14:29:06 +0100	[thread overview]
Message-ID: <20180125132906.GA10968@localhost.localdomain> (raw)
In-Reply-To: <20180125122458.GB3420@rei>

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

WARNING: multiple messages have this Message-ID (diff)
From: Juri Lelli <juri.lelli@redhat.com>
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	[thread overview]
Message-ID: <20180125132906.GA10968@localhost.localdomain> (raw)
In-Reply-To: <20180125122458.GB3420@rei>

[-- Attachment #1: Type: text/plain, Size: 396 bytes --]

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

WARNING: multiple messages have this Message-ID (diff)
From: Juri Lelli <juri.lelli@redhat.com>
To: Cyril Hrubis <chrubis@suse.cz>
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
Date: Thu, 25 Jan 2018 14:29:06 +0100	[thread overview]
Message-ID: <20180125132906.GA10968@localhost.localdomain> (raw)
In-Reply-To: <20180125122458.GB3420@rei>

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

  reply	other threads:[~2018-01-25 13:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-25  6:28 [LTP] [lkp-robot] [sched/deadline] e0367b1267: WARNING:at_kernel/sched/sched.h:#assert_clock_updated kernel test robot
2018-01-25  6:28 ` kernel test robot
2018-01-25  6:28 ` kernel test robot
2018-01-25 11:20 ` [LTP] " Juri Lelli
2018-01-25 11:20   ` Juri Lelli
2018-01-25 11:20   ` Juri Lelli
2018-01-25 12:24   ` [LTP] " Cyril Hrubis
2018-01-25 12:24     ` Cyril Hrubis
2018-01-25 12:24     ` Cyril Hrubis
2018-01-25 13:29     ` Juri Lelli [this message]
2018-01-25 13:29       ` Juri Lelli
2018-01-25 13:29       ` Juri Lelli
2018-01-25 13:35       ` Cyril Hrubis
2018-01-25 13:35         ` Cyril Hrubis
2018-01-25 13:35         ` Cyril Hrubis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180125132906.GA10968@localhost.localdomain \
    --to=juri.lelli@redhat.com \
    --cc=ltp@lists.linux.it \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.