Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753524AbXKSVRS (ORCPT ); Mon, 19 Nov 2007 16:17:18 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751750AbXKSVRK (ORCPT ); Mon, 19 Nov 2007 16:17:10 -0500 Received: from e5.ny.us.ibm.com ([32.97.182.145]:39835 "EHLO e5.ny.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751710AbXKSVRJ (ORCPT ); Mon, 19 Nov 2007 16:17:09 -0500 Subject: Re: [Patch] mm/sparse.c: Check the return value of sparse_index_alloc(). From: Dave Hansen To: WANG Cong Cc: LKML , Rik van Riel , Christoph Lameter , Andrew Morton , linux-mm@kvack.org In-Reply-To: <20071115135428.GE2489@hacking> References: <20071115135428.GE2489@hacking> Content-Type: text/plain Date: Mon, 19 Nov 2007 13:17:02 -0800 Message-Id: <1195507022.27759.146.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.10.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1336 Lines: 40 On Thu, 2007-11-15 at 21:54 +0800, WANG Cong wrote: > Since sparse_index_alloc() can return NULL on memory allocation failure, > we must deal with the failure condition when calling it. > > Signed-off-by: WANG Cong > Cc: Christoph Lameter > Cc: Rik van Riel > > --- > > diff --git a/Makefile b/Makefile > diff --git a/mm/sparse.c b/mm/sparse.c > index e06f514..d245e59 100644 > --- a/mm/sparse.c > +++ b/mm/sparse.c > @@ -83,6 +83,8 @@ static int __meminit sparse_index_init(unsigned long section_nr, int nid) > return -EEXIST; > > section = sparse_index_alloc(nid); > + if (!section) > + return -ENOMEM; > /* > * This lock keeps two different sections from > * reallocating for the same index Oddly enough, sparse_add_one_section() doesn't seem to like to check its allocations. The usemap is checked, but not freed on error. If you want to fix this up, I think it needs a little more love than just two lines. Do you want to try to add some actual error handling to sparse_add_one_section()? -- Dave - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/