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]

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

On Wed, Dec 10, 2014 at 10:03:57AM -0500, Pranith Kumar wrote:
> On 12/10/2014 03:09 AM, Stephen Rothwell wrote:
> > Hi Paul,
> > 
> > After merging the rcu tree, today's linux-next build (powerpc64
> > allnoconfig) failed like this:
> > 
> > In file included from arch/powerpc/include/asm/kvm_ppc.h:30:0,
> >                  from arch/powerpc/kernel/setup_64.c:68:
> > include/linux/kvm_host.h:366:21: error: field 'srcu' has incomplete type
> >   struct srcu_struct srcu;
> >                      ^
> > include/linux/kvm_host.h:367:21: error: field 'irq_srcu' has incomplete type
> >   struct srcu_struct irq_srcu;
> >                      ^
> > 
> > Presumably caused by commit 6e8ef258b669 ("srcu: Isolate srcu sections
> > using CONFIG_SRCU").
> > 
> > I have reverted that commit again for today - more work required ...
> > 
> 
> Looks like there are other places which use KVM unconditionally. I will try to look and fix such uses. 
> 
> Paul, can you drop the patch until then? Thanks!

Done!

							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/