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
| ||
|
Date: Wed, 25 Aug 2010 10:18:31 +0200 From: Tejun Heo <tj@...nel.org> To: Christoph Lameter <cl@...ux.com> CC: Pekka Enberg <penberg@...helsinki.fi>, 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 final tree (slab tree related) Hello, On 08/24/2010 08:53 PM, Christoph Lameter wrote: >> [ 0.000000] Kernel panic - not syncing: Cannot create slab kmem_cache >> size=232 realsize=256 order=0 offset=0 flags=42000 > > alloc per cpu result in kmalloc which fails. > > Tejon: Is there some way we could get a reserved per cpu area under UP > instead of fallback to slab allocations during bootup? Eh... nasty. Maybe we can create a alloc_percpu_early() function which doesn't allow freeing of allocate memory and just redirect to bootmem on UP? -- tejun -- 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/
Powered by blists - more mailing lists