From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751922AbaAON0S (ORCPT ); Wed, 15 Jan 2014 08:26:18 -0500 Received: from mga02.intel.com ([134.134.136.20]:18102 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751806AbaAON0P (ORCPT ); Wed, 15 Jan 2014 08:26:15 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.95,663,1384329600"; d="scan'208";a="459194848" Date: Wed, 15 Jan 2014 21:26:09 +0800 From: Fengguang Wu To: Peter Zijlstra Cc: Dario Faggioli , Juri Lelli , LKML , lkp@linux.intel.com Subject: Re: [sched] d50dde5a1: LTP sched_setparam* TFAILs Message-ID: <20140115132609.GA28334@localhost> References: <20140115124739.GB19419@localhost> <20140115130938.GF31570@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140115130938.GF31570@twins.programming.kicks-ass.net> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 15, 2014 at 02:09:38PM +0100, Peter Zijlstra wrote: > On Wed, Jan 15, 2014 at 08:47:39PM +0800, Fengguang Wu wrote: > > Hi Dario, > > > > We notice the below LTP failures since commit d50dde5a1 ("sched: Add > > new scheduler syscalls to support an extended scheduling parameters > > ABI") in tip tree's sched/core branch: > > > > ltp.sched_setparam02.1.TFAIL > > ltp.sched_setparam02.2.TFAIL > > ltp.sched_setparam02.3.TFAIL > > ltp.sched_setparam03.1.TFAIL > > > > It seems that the LKP test failures are somehow expected due to the > > change of ABI. However it does mean that these test cases will need to > > be updated. > > So with LTP from https://github.com/linux-test-project/ltp.git > and a tip/master build, I get: > > root@westmere:/usr/local/src/ltp/testcases/kernel/syscalls/sched_setscheduler# ./sched_setscheduler01 > sched_setscheduler01 1 TPASS : expected failure - errno = 3 : No such process > sched_setscheduler01 2 TPASS : expected failure - errno = 22 : Invalid argument > sched_setscheduler01 3 TPASS : expected failure - errno = 14 : Bad address > sched_setscheduler01 4 TPASS : expected failure - errno = 22 : Invalid argument > root@westmere:/usr/local/src/ltp/testcases/kernel/syscalls/sched_setscheduler# ./sched_setscheduler02 > sched_setscheduler02 1 TPASS : got EPERM It's sched_setparam02 that TFAIL, not sched_setscheduler02. :) Thanks, Fengguang