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: Thu, 27 Dec 2012 15:04:12 -0800 (PST) From: David Rientjes <rientjes@...gle.com> To: Sasha Levin <sasha.levin@...cle.com> cc: Andrew Morton <akpm@...ux-foundation.org>, Johannes Weiner <hannes@...xchg.org>, "David S. Miller" <davem@...emloft.net>, Tejun Heo <tj@...nel.org>, Joonsoo Kim <js1304@...il.com>, Yinghai Lu <yinghai@...nel.org>, linux-mm@...ck.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 2/3] mm, bootmem: panic in bootmem alloc functions even if slab is available On Thu, 27 Dec 2012, Sasha Levin wrote: > That's exactly what happens with the patch. Note that in the current upstream > version there are several slab checks scattered all over. > > In this case for example, I'm removing it from __alloc_bootmem_node(), but the > first code line of__alloc_bootmem_node_nopanic() is: > > if (WARN_ON_ONCE(slab_is_available())) > return kzalloc(size, GFP_NOWAIT); > You're only talking about mm/bootmem.c and not mm/nobootmem.c, and notice that __alloc_bootmem_node() does not call __alloc_bootmem_node_nopanic(), it calls ___alloc_bootmem_node_nopanic(). -- 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