From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: Re: [rcu:dev 119/161] ERROR: "rcu_barrier" [fs/isofs/isofs.ko] undefined!
Date: Wed, 4 Jul 2018 04:31:00 -0700 [thread overview]
Message-ID: <20180704113100.GI3593@linux.vnet.ibm.com> (raw)
In-Reply-To: <201807040653.xcSP674j%fengguang.wu@intel.com>
On Wed, Jul 04, 2018 at 06:20:56AM +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev
> head: 472755d5ff3ee21ad16e0a0a06e087b7569eaffe
> commit: 16bf6b3b61864e444bae5e4a7cf121f777893a8c [119/161] rcu: Express Tiny RCU updates in terms of RCU rather than RCU-sched
> config: um-x86_64_defconfig (attached as .config)
> compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
> reproduce:
> git checkout 16bf6b3b61864e444bae5e4a7cf121f777893a8c
> # save the attached .config to linux build tree
> make ARCH=um SUBARCH=x86_64
>
> All errors (new ones prefixed by >>):
>
> >> ERROR: "rcu_barrier" [fs/isofs/isofs.ko] undefined!
Gah! I forgot to update the EXPORT_SYMBOL_GPL() to match the
function name. Good catch, will fix, thank you!
Thanx, Paul
prev parent reply other threads:[~2018-07-04 11:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 22:20 kbuild test robot
2018-07-04 11:31 ` Paul E. McKenney [this message]
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=20180704113100.GI3593@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome