[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20071116133714.876f5246.akpm@linux-foundation.org>
Date: Fri, 16 Nov 2007 13:37:14 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: WANG Cong <xiyou.wangcong@...il.com>
Cc: linux-kernel@...r.kernel.org, riel@...hat.com, clameter@....com,
linux-mm@...ck.org
Subject: Re: [Patch] mm/sparse.c: Check the return value of
sparse_index_alloc().
On Thu, 15 Nov 2007 21:54:28 +0800
WANG Cong <xiyou.wangcong@...il.com> 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 <xiyou.wangcong@...il.com>
> Cc: Christoph Lameter <clameter@....com>
> Cc: Rik van Riel <riel@...hat.com>
>
> ---
>
> 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
Sure, but both callers of sparse_index_init() ignore its return value anyway.
-
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