The patch titled
hugetlb: Fix dynamic pool resize failure case (update)
has been added to the -mm tree. Its filename is
hugetlb-fix-dynamic-pool-resize-failure-case-update.patch
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
------------------------------------------------------
Subject: hugetlb: Fix dynamic pool resize failure case (update)
From: Adam Litke <agl@xxxxxxxxxx>
Added a comment explaining the free logic in gather_surplus_pages.
Signed-off-by: Adam Litke <agl@xxxxxxxxxx>
Acked-by: Dave Hansen <haveblue@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
mm/hugetlb.c | 6 ++++++
1 file changed, 6 insertions(+)
diff -puN mm/hugetlb.c~hugetlb-fix-dynamic-pool-resize-failure-case-update mm/hugetlb.c
--- a/mm/hugetlb.c~hugetlb-fix-dynamic-pool-resize-failure-case-update
+++ a/mm/hugetlb.c
@@ -303,6 +303,12 @@ free:
if ((--needed) >= 0)
enqueue_huge_page(page);
else {
+ /*
+ * Decrement the refcount and free the page using its
+ * destructor. This must be done with hugetlb_lock
+ * unlocked which is safe because free_huge_page takes
+ * hugetlb_lock before deciding how to free the page.
+ */
spin_unlock(&hugetlb_lock);
put_page(page);
spin_lock(&hugetlb_lock);
_
Patches currently in -mm which might be from agl@xxxxxxxxxx are
hugetlb-move-update_and_free_page.patch
hugetlb-try-to-grow-hugetlb-pool-for-map_private-mappings.patch
hugetlb-try-to-grow-hugetlb-pool-for-map_shared-mappings.patch
hugetlb-add-hugetlb_dynamic_pool-sysctl.patch
hugetlb-allow-extending-ftruncate-on-hugetlbfs.patch
hugetlbfs-read-support-fix-2-fix.patch
hugetlb-fix-pool-resizing-corner-case-v2.patch
hugetlb-fix-hugepage-allocation-with-memoryless-nodes.patch
hugetlb-fix-dynamic-pool-resize-failure-case.patch
hugetlb-fix-dynamic-pool-resize-failure-case-update.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
