linux-kernel - Re: linux-next: build failure after merge of the rcu tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 9 Dec 2014 06:07:33 -0800
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Pranith Kumar <bobby.prani@...il.com>
Subject: Re: linux-next: build failure after merge of the rcu tree

On Tue, Dec 09, 2014 at 10:42:30PM +1100, Stephen Rothwell wrote:
> Hi Paul,
> 
> After merging the rcu tree, today's linux-next build (powerpc
> allnoconfig) failed like this:
> 
> include/linux/notifier.h:51:4: warning: its scope is only this definition or declaration, which is probably not what you want
> In file included from include/linux/memory_hotplug.h:6:0,
>                  from include/linux/mmzone.h:790,
>                  from include/linux/gfp.h:5,
>                  from arch/powerpc/mm/pgtable.c:25:
> include/linux/notifier.h:51:4: error: 'struct notifier_block' declared inside parameter list [-Werror]
>     unsigned long action, void *data);
>     ^
> 
> And many more (most just warnings ...).
> 
> Presumably caused by commit 44dec3761b63 ("srcu: Isolate srcu sections
> using CONFIG_SRCU") and reverting that commit makes the messages go
> away, so I have done that for today.

Apologies, I forgot to push the fix to rcu/next, will do.

							Thanx, Paul

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