Messages in this thread | | | Date | Tue, 1 Sep 2015 22:26:13 -0700 | From | "Paul E. McKenney" <> | Subject | Re: linux-next: build failure after merge of the rcu tree |
| |
On Wed, Sep 02, 2015 at 01:58:00PM +1000, Stephen Rothwell wrote: > Hi Paul, > > On Tue, 1 Sep 2015 00:49:46 -0700 "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> 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.
OK, now I actually have deferred these to v4.4.
Davidlohr, the error is due to sched_setscheduler_nocheck() not being exported, so that Stephen gets this failure when building modules. This is 04be76a9b067 (locktorture: Support rtmutex torturing) in -rcu.
Thoughts?
Thanx, Paul
| |