linux-kernel - Re: rcu_init allocation failure trace on bootup

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: <20130506215629.GA20273@redhat.com>
Date:	Mon, 6 May 2013 17:56:29 -0400
From:	Dave Jones <davej@...hat.com>
To:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: rcu_init allocation failure trace on bootup

On Mon, May 06, 2013 at 02:02:49PM -0700, Paul E. McKenney wrote:

 > >  > You are quite right, I am getting ahead of myself.  Please see below
 > >  > for the patch.
 > > 
 > > Doesn't fix it for me.
 > > 
 > > Is it this one instead perhaps ?
 > > 
 > >   89 #ifndef CONFIG_RCU_NOCB_CPU_NONE
 > >   90         if (!have_rcu_nocb_mask) {
 > >   91                 alloc_bootmem_cpumask_var(&rcu_nocb_mask);
 > >   92                 have_rcu_nocb_mask = true;
 > >   93         }
 > 
 > Hmmm...  That was in fact the one that the patch was intended to change.
 > Just out of curiosity, where did the patch apply instead?

I think this might be my screwup. I did it by hand, and misapplied it
to the top of rcu_nocb_setup() instead.

	Dave

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