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 for Android: free password hash cracker in your pocket

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

Message-ID: <20150413113405.GA667@gmail.com>
Date:	Mon, 13 Apr 2015 13:34:05 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Borislav Petkov <bp@...e.de>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: build failure after merge of the rcu tree


* Borislav Petkov <bp@...e.de> wrote:

> On Mon, Apr 13, 2015 at 08:39:17PM +1000, Stephen Rothwell wrote:
> > Hi Paul,
> > 
> > After merging the rcu tree, today's linux-next build (powerpc allnoconfig)
> > failed like this:
> > 
> > init/main.c: In function 'rest_init':
> > init/main.c:387:2: error: implicit declaration of function 'smpboot_thread_init' [-Werror=implicit-function-declaration]
> >   smpboot_thread_init();
> >   ^
> > 
> > Caused by commit c55f6e1f6f69 ("cpu: Defer smpboot kthread unparking
> > until CPU known to scheduler").  The declaration in include/linux/cpu.h
> > is protected by CONFIG_SMP, its use is not.
> > 
> > I have reverted that commit for today.
> 
> Thanks for the report Stephen, I know today is the day of b0rked
> linux-next builds :-(
> 
> I think Ingo merged Paul's patch already so here's a fix ontop:

Yeah, I too triggered that build failure and fixed it locally.

Thanks,

	Ingo
--
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/