Subject: [merged] mm-memoryc-update-comment-in-unmap_single_vma.patch removed from -mm tree
To: davidlohr@xxxxxx,mm-commits@xxxxxxxxxxxxxxx
From: akpm@xxxxxxxxxxxxxxxxxxxx
Date: Tue, 08 Apr 2014 13:34:19 -0700
The patch titled
Subject: mm/memory.c: update comment in unmap_single_vma()
has been removed from the -mm tree. Its filename was
mm-memoryc-update-comment-in-unmap_single_vma.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Davidlohr Bueso <davidlohr@xxxxxx>
Subject: mm/memory.c: update comment in unmap_single_vma()
The described issue now occurs inside mmap_region(). And unfortunately is
still valid.
Signed-off-by: Davidlohr Bueso <davidlohr@xxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
mm/memory.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -puN mm/memory.c~mm-memoryc-update-comment-in-unmap_single_vma mm/memory.c
--- a/mm/memory.c~mm-memoryc-update-comment-in-unmap_single_vma
+++ a/mm/memory.c
@@ -1320,9 +1320,9 @@ static void unmap_single_vma(struct mmu_
* It is undesirable to test vma->vm_file as it
* should be non-null for valid hugetlb area.
* However, vm_file will be NULL in the error
- * cleanup path of do_mmap_pgoff. When
+ * cleanup path of mmap_region. When
* hugetlbfs ->mmap method fails,
- * do_mmap_pgoff() nullifies vma->vm_file
+ * mmap_region() nullifies vma->vm_file
* before calling this function to clean up.
* Since no pte has actually been setup, it is
* safe to do nothing in this case.
_
Patches currently in -mm which might be from davidlohr@xxxxxx are
origin.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
