From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752095Ab2LTUiR (ORCPT ); Thu, 20 Dec 2012 15:38:17 -0500 Received: from userp1040.oracle.com ([156.151.31.81]:50263 "EHLO userp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752019Ab2LTUiN (ORCPT ); Thu, 20 Dec 2012 15:38:13 -0500 Message-ID: <50D376E9.9030507@oracle.com> Date: Thu, 20 Dec 2012 15:36:57 -0500 From: Sasha Levin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: David Rientjes CC: Andrew Morton , Johannes Weiner , Michal Hocko , Gavin Shan , linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] mm/sparse: don't check return value of alloc_bootmem calls References: <1356030701-16284-1-git-send-email-sasha.levin@oracle.com> <1356030701-16284-30-git-send-email-sasha.levin@oracle.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Source-IP: ucsinet21.oracle.com [156.151.31.93] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/20/2012 03:23 PM, David Rientjes wrote: > On Thu, 20 Dec 2012, Sasha Levin wrote: > >> diff --git a/mm/sparse.c b/mm/sparse.c >> index 6b5fb76..ae64d6e 100644 >> --- a/mm/sparse.c >> +++ b/mm/sparse.c >> @@ -403,15 +403,13 @@ void __init sparse_mem_maps_populate_node(struct page **map_map, >> size = PAGE_ALIGN(size); >> map = __alloc_bootmem_node_high(NODE_DATA(nodeid), size * map_count, >> PAGE_SIZE, __pa(MAX_DMA_ADDRESS)); >> - if (map) { >> - for (pnum = pnum_begin; pnum < pnum_end; pnum++) { >> - if (!present_section_nr(pnum)) >> - continue; >> - map_map[pnum] = map; >> - map += size; >> - } >> - return; >> + for (pnum = pnum_begin; pnum < pnum_end; pnum++) { >> + if (!present_section_nr(pnum)) >> + continue; >> + map_map[pnum] = map; >> + map += size; >> } >> + return; >> >> /* fallback */ >> for (pnum = pnum_begin; pnum < pnum_end; pnum++) { > > That's not true when slab_is_available() and why would you possibly add a > return statement right before fallback code in such cases? So what we really need is to update the documentation of __alloc_bootmem_node, I'll send a patch that does that instead. I've dragged the 'return' out of the if(map) condition, I should have removed the fallback as well and so the return would also be gone, but that's irrelevant now. Thanks, Sasha