linux-kernel - Re: RCU init call bootmem allocation after slub us ready.

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAE9FiQXgmFbybdK6mXUrh=zQw6kPbxLh0qGWKMGGVy+jhDZYSA@mail.gmail.com>
Date:	Mon, 6 May 2013 13:00:08 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	Paul McKenney <paulmck@...ux.vnet.ibm.com>
Cc:	Ingo Molnar <mingo@...e.hu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: RCU init call bootmem allocation after slub us ready.

On Mon, May 6, 2013 at 12:06 PM, Paul E. McKenney
<paulmck@...ux.vnet.ibm.com> wrote:

> Do you have commit fa0f93cd6a (rcu: Don't allocate bootmem from rcu_init())?
> If not, could you please try applying it?

oh, must be in tip/rcu branch...

i only test tip/x86 for a while.

sorry for the noise.

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