[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50DCD4CB.50205@oracle.com>
Date: Thu, 27 Dec 2012 18:07:55 -0500
From: Sasha Levin <sasha.levin@...cle.com>
To: David Rientjes <rientjes@...gle.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 12/27/2012 06:04 PM, David Rientjes wrote:
> 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().
Holy cow, this is an underscore hell.
Thanks,
Sasha
--
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