From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752612AbbIBD6G (ORCPT ); Tue, 1 Sep 2015 23:58:06 -0400 Received: from ozlabs.org ([103.22.144.67]:36324 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752344AbbIBD6E (ORCPT ); Tue, 1 Sep 2015 23:58:04 -0400 Date: Wed, 2 Sep 2015 13:58:00 +1000 From: Stephen Rothwell To: "Paul E. McKenney" Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Davidlohr Bueso Subject: Re: linux-next: build failure after merge of the rcu tree Message-ID: <20150902135800.068f0f4a@canb.auug.org.au> In-Reply-To: <20150901074946.GF4029@linux.vnet.ibm.com> References: <20150901135006.78be270e@canb.auug.org.au> <20150901074946.GF4029@linux.vnet.ibm.com> X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Paul, On Tue, 1 Sep 2015 00:49:46 -0700 "Paul E. McKenney" wrote: > > On Tue, Sep 01, 2015 at 01:50:06PM +1000, Stephen Rothwell wrote: > > > > After merging the rcu tree, today's linux-next build (x86_64 allmodconfig) > > failed like this: > > > > ERROR: "sched_setscheduler_nocheck" [kernel/locking/locktorture.ko] undefined! > > ERROR: "percpu_down_write" [kernel/locking/locktorture.ko] undefined! > > ERROR: "percpu_up_write" [kernel/locking/locktorture.ko] undefined! > > ERROR: "percpu_down_read" [kernel/locking/locktorture.ko] undefined! > > ERROR: "percpu_up_read" [kernel/locking/locktorture.ko] undefined! > > ERROR: "__percpu_init_rwsem" [kernel/locking/locktorture.ko] undefined! > > > > Caused by commits > > > > 04be76a9b067 ("locktorture: Support rtmutex torturing") > > 40b2996f9b32 ("locktorture: Add torture tests for percpu_rwsem") > > > > and maybe more. > > > > I have used the rcu tree from next-20150831 for today. > > It is looking like I will be deferring these to v4.4, apologies for > the hassle! This still fails to build but now I only get the error about sched_setscheduler_nocheck. -- Cheers, Stephen Rothwell sfr@canb.auug.org.au