Re: [PATCH] mm, vmalloc: fix high order __GFP_NOFAIL allocations

[Michal Hocko]

Thanks. Here is an incremental diff
diff --git a/mm/vmalloc.c b/mm/vmalloc.c
index bef6cf2b4d46..b01295672a31 100644
--- a/mm/vmalloc.c
+++ b/mm/vmalloc.c
@@ -2938,7 +2938,7 @@ vm_area_alloc_pages(gfp_t gfp, int nid,
 		/*
 		 * Higher order nofail allocations are really expensive and
 		 * potentially dangerous (pre-mature OOM, disruptive reclaim
-		 * and compaction etc.
+		 * and compaction etc).
 		 */
 		alloc_gfp &= ~__GFP_NOFAIL;
 		nofail = true;
@@ -2965,7 +2965,7 @@ vm_area_alloc_pages(gfp_t gfp, int nid,
 
 		/*
 		 * Higher order allocations must be able to be treated as
-		 * indepdenent small pages by callers (as they can with
+		 * independent small pages by callers (as they can with
 		 * small-page vmallocs). Some drivers do their own refcounting
 		 * on vmalloc_to_page() pages, some use page->mapping,
 		 * page->lru, etc.
-- 
Michal Hocko
SUSE Labs