The patch titled
Subject: mm/memory.c:print_vma_addr(): call up_read(&mm->mmap_sem) directly
has been added to the -mm tree. Its filename is
mm-memoryc-print_vma_addr-call-up_readmm-mmap_sem-directly.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Jeff Liu <jeff.liu@xxxxxxxxxx>
Subject: mm/memory.c:print_vma_addr(): call up_read(&mm->mmap_sem) directly
Call up_read(&mm->mmap_sem) directly since we have already got mm via
current->mm at the beginning of print_vma_addr().
Signed-off-by: Jie Liu <jeff.liu@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
mm/memory.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN mm/memory.c~mm-memoryc-print_vma_addr-call-up_readmm-mmap_sem-directly mm/memory.c
--- a/mm/memory.c~mm-memoryc-print_vma_addr-call-up_readmm-mmap_sem-directly
+++ a/mm/memory.c
@@ -3946,7 +3946,7 @@ void print_vma_addr(char *prefix, unsign
free_page((unsigned long)buf);
}
}
- up_read(¤t->mm->mmap_sem);
+ up_read(&mm->mmap_sem);
}
#ifdef CONFIG_PROVE_LOCKING
_
Subject: Subject: mm/memory.c:print_vma_addr(): call up_read(&mm->mmap_sem) directly
Patches currently in -mm which might be from jeff.liu@xxxxxxxxxx are
linux-next.patch
mm-memoryc-print_vma_addr-call-up_readmm-mmap_sem-directly.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
