Re: linux-next: build warning after merge of the akpm tree

[Davidlohr Bueso]

On Tue, 2014-05-20 at 07:36 +1000, Stephen Rothwell wrote:
> Hi,
> 
> On Mon, 19 May 2014 08:13:16 -0700 Davidlohr Bueso <davidlohr@xxxxxx> wrote:
> >
> > On Mon, 2014-05-19 at 18:13 +1000, Stephen Rothwell wrote:
> > > Hi Andrew,
> > > 
> > > After merging the akpm tree, today's linux-next build (arm
> > > multi_v7_defconfig) produced these warnings:
> > > 
> > > 
> > > ipc/ipcns_notifier.c:22:8: warning: excess elements in struct initializer [enabled by default]
> > > ipc/ipcns_notifier.c:22:8: warning: (near initialization for 'ipcns_chain.rwsem') [enabled by default]
> > > ipc/ipcns_notifier.c:22:8: warning: excess elements in struct initializer [enabled by default]
> > > ipc/ipcns_notifier.c:22:8: warning: (near initialization for 'ipcns_chain.rwsem') [enabled by default]
> > > 
> > > and many more in other files ...
> > 
> > Hmm are all the warning the same? Is this just on arm? have you seen it
> > in other archs? (Could you please send me the .config)
> 
> The warnings were all the same, I saw it only on arm (since that was
> what I built) and I mentioned the config above.
> 
> > > Presumably a result of commit fe2038c57c03 ("rwsem: Support optimistic
> > > spinning").
> > 
> > If CONFIG_SMP, we add two new fields to the rwsem structure
> > (include/linux/rwsem.h) and likewise we update the
> > __RWSEM_INITIALIZER(name) macro. Afaict the only way to trigger
> > something like that is to be using the spinlock variant
> > (rwsem-spinlock.h).
> 
> Actually quite a few architectures do set
> CONFIG_RWSEM_GENERIC_SPINLOCK, and so wouldn't it make more sense to
> actually directly test that?

Both are equivalent, I have no preference. I've sent a formal fix to the
-tip folks, I guess I'll let them choose.

Thanks,
Davidlohr

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/