The patch titled
     mm/sparse.c: check the return value of sparse_index_alloc()
has been removed from the -mm tree.  Its filename was
     mm-sparsec-check-the-return-value-of-sparse_index_alloc.patch

This patch was dropped because it was merged into mainline or a subsystem tree

------------------------------------------------------
Subject: mm/sparse.c: check the return value of sparse_index_alloc()
From: WANG Cong <[EMAIL PROTECTED]>

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 <[EMAIL PROTECTED]>
Cc: Christoph Lameter <[EMAIL PROTECTED]>
Cc: Rik van Riel <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---

 mm/sparse.c |    2 ++
 1 file changed, 2 insertions(+)

diff -puN mm/sparse.c~mm-sparsec-check-the-return-value-of-sparse_index_alloc 
mm/sparse.c
--- a/mm/sparse.c~mm-sparsec-check-the-return-value-of-sparse_index_alloc
+++ a/mm/sparse.c
@@ -83,6 +83,8 @@ static int __meminit sparse_index_init(u
                return -EEXIST;
 
        section = sparse_index_alloc(nid);
+       if (!section)
+               return -ENOMEM;
        /*
         * This lock keeps two different sections from
         * reallocating for the same index
_

Patches currently in -mm which might be from [EMAIL PROTECTED] are

origin.patch
uml-code-tidying-under-arch-um-os-linux.patch
uml-const-and-other-tidying.patch
time-fix-sysfs_show_availablecurrent_clocksources-buffer-overflow-problem.patch

-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to