From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: Re: [rcu:dev.2017.04.28a 41/45] include/linux/notifier.h:77:21: error: field 'srcu' has incomplete type
Date: Sat, 29 Apr 2017 20:33:20 -0700 [thread overview]
Message-ID: <20170430033320.GN3956@linux.vnet.ibm.com> (raw)
In-Reply-To: <201704300701.Q1l6R9fl%fengguang.wu@intel.com>
On Sun, Apr 30, 2017 at 07:32:17AM +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2017.04.28a
> head: 1205059ca5d4835e9213ff943ce3a51980718b5d
> commit: e01ef0529ed548c1b30206058c2b5eecbbc07998 [41/45] srcu: Make SRCU be once again optional
> config: sparc64-allnoconfig (attached as .config)
> compiler: sparc64-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
> reproduce:
> wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout e01ef0529ed548c1b30206058c2b5eecbbc07998
> # save the attached .config to linux build tree
> make.cross ARCH=sparc64
>
> All errors (new ones prefixed by >>):
>
> In file included from include/linux/memory_hotplug.h:6:0,
> from include/linux/mmzone.h:749,
> from include/linux/gfp.h:5,
> from include/linux/kmod.h:22,
> from include/linux/module.h:13,
> from init/main.c:16:
> >> include/linux/notifier.h:77:21: error: field 'srcu' has incomplete type
> struct srcu_struct srcu;
> ^~~~
Hmmm...
This sort of thing has been legal for quite some time, so I am taking
the crude step of providing an empty definition for srcu_struct when
building with CONFIG_SRCU=n.
Thanx, Paul
> vim +/srcu +77 include/linux/notifier.h
>
> e041c6834 Alan Stern 2006-03-27 61 struct atomic_notifier_head {
> e041c6834 Alan Stern 2006-03-27 62 spinlock_t lock;
> 374a8e0dc Arnd Bergmann 2010-02-24 63 struct notifier_block __rcu *head;
> e041c6834 Alan Stern 2006-03-27 64 };
> e041c6834 Alan Stern 2006-03-27 65
> e041c6834 Alan Stern 2006-03-27 66 struct blocking_notifier_head {
> e041c6834 Alan Stern 2006-03-27 67 struct rw_semaphore rwsem;
> 374a8e0dc Arnd Bergmann 2010-02-24 68 struct notifier_block __rcu *head;
> e041c6834 Alan Stern 2006-03-27 69 };
> e041c6834 Alan Stern 2006-03-27 70
> e041c6834 Alan Stern 2006-03-27 71 struct raw_notifier_head {
> 374a8e0dc Arnd Bergmann 2010-02-24 72 struct notifier_block __rcu *head;
> e041c6834 Alan Stern 2006-03-27 73 };
> e041c6834 Alan Stern 2006-03-27 74
> eabc06940 Alan Stern 2006-10-04 75 struct srcu_notifier_head {
> eabc06940 Alan Stern 2006-10-04 76 struct mutex mutex;
> eabc06940 Alan Stern 2006-10-04 @77 struct srcu_struct srcu;
> 374a8e0dc Arnd Bergmann 2010-02-24 78 struct notifier_block __rcu *head;
> eabc06940 Alan Stern 2006-10-04 79 };
> eabc06940 Alan Stern 2006-10-04 80
> e041c6834 Alan Stern 2006-03-27 81 #define ATOMIC_INIT_NOTIFIER_HEAD(name) do { \
> e041c6834 Alan Stern 2006-03-27 82 spin_lock_init(&(name)->lock); \
> e041c6834 Alan Stern 2006-03-27 83 (name)->head = NULL; \
> e041c6834 Alan Stern 2006-03-27 84 } while (0)
> e041c6834 Alan Stern 2006-03-27 85 #define BLOCKING_INIT_NOTIFIER_HEAD(name) do { \
>
> :::::: The code at line 77 was first introduced by commit
> :::::: eabc069401bcf45bcc3f19e643017bf761780aa8 [PATCH] Add SRCU-based notifier chains
>
> :::::: TO: Alan Stern <stern@rowland.harvard.edu>
> :::::: CC: Linus Torvalds <torvalds@g5.osdl.org>
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
prev parent reply other threads:[~2017-04-30 3:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-29 23:32 [rcu:dev.2017.04.28a 41/45] include/linux/notifier.h:77:21: error: field 'srcu' has incomplete type kbuild test robot
2017-04-30 3:33 ` 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=20170430033320.GN3956@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
/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