Subject: [merged] 
mm-hugetlbc-add-cond_resched_lock-in-return_unused_surplus_pages.patch removed 
from -mm tree
To: 
[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected]
From: [email protected]
Date: Mon, 21 Apr 2014 11:11:05 -0700


The patch titled
     Subject: mm/hugetlb.c: add cond_resched_lock() in 
return_unused_surplus_pages()
has been removed from the -mm tree.  Its filename was
     mm-hugetlbc-add-cond_resched_lock-in-return_unused_surplus_pages.patch

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

------------------------------------------------------
From: "Mizuma, Masayoshi" <[email protected]>
Subject: mm/hugetlb.c: add cond_resched_lock() in return_unused_surplus_pages()

soft lockup in freeing gigantic hugepage fixed in commit 55f67141a892 "mm:
hugetlb: fix softlockup when a large number of hugepages are freed." can
happen in return_unused_surplus_pages(), so let's fix it.

Signed-off-by: Masayoshi Mizuma <[email protected]>
Signed-off-by: Naoya Horiguchi <[email protected]>
Cc: Joonsoo Kim <[email protected]>
Cc: Michal Hocko <[email protected]>
Cc: Aneesh Kumar <[email protected]>
Cc: KOSAKI Motohiro <[email protected]>
Cc: <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
---

 mm/hugetlb.c |    1 +
 1 file changed, 1 insertion(+)

diff -puN 
mm/hugetlb.c~mm-hugetlbc-add-cond_resched_lock-in-return_unused_surplus_pages 
mm/hugetlb.c
--- 
a/mm/hugetlb.c~mm-hugetlbc-add-cond_resched_lock-in-return_unused_surplus_pages
+++ a/mm/hugetlb.c
@@ -1172,6 +1172,7 @@ static void return_unused_surplus_pages(
        while (nr_pages--) {
                if (!free_pool_huge_page(h, &node_states[N_MEMORY], 1))
                        break;
+               cond_resched_lock(&hugetlb_lock);
        }
 }
 
_

Patches currently in -mm which might be from [email protected] are


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

Reply via email to