[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20210317142350.GC2696@paulmck-ThinkPad-P72>
Date: Wed, 17 Mar 2021 07:23:50 -0700
From: "Paul E. McKenney" <paulmck@...nel.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the rcu tree
On Wed, Mar 17, 2021 at 04:36:13PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the rcu tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> ERROR: modpost: "rcu_read_lock_longwait_held" [kernel/rcu/rcutorture.ko] undefined!
> ERROR: modpost: "rcu_read_unlock_longwait" [kernel/rcu/rcutorture.ko] undefined!
> ERROR: modpost: "rcu_read_lock_longwait" [kernel/rcu/rcutorture.ko] undefined!
>
> Caused by commit
>
> bd6ae31d1b1f ("rcutorture: Add the ability to torture RCU longsleep")
>
> CONFIG_LONGWAIT_RCU=y
> CONFIG_RCU_TORTURE_TEST=m
>
> I have used the rcu tree from next-20210316 for today.
Gah! Rebase first, then retest, -then- adjust rcu/next...
Will fix, apologies for the hassle!
Thanx, Paul
Powered by blists - more mailing lists