mm/madvise: use vma_lookup() instead of find_vma()

Using vma_lookup() verifies the start address is contained in the found
vma.  This results in easier to read the code.

Link: https://lkml.kernel.org/r/20220311082731.63513-1-linmiaohe@huawei.com
Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
Reviewed-by: David Hildenbrand <david@redhat.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

diff --git a/mm/madvise.c b/mm/madvise.c
index 7b5d6fc99a9003b8ec1da3729a86fd8628e9e62d..2efcde2d7e4cad32b923c0cae11adbfc706252ac 100644 (file)
--- a/mm/madvise.c
+++ b/mm/madvise.c
@@ -849,8 +849,8 @@ static long madvise_populate(struct vm_area_struct *vma,
                 * our VMA might have been split.
                 */
                if (!vma || start >= vma->vm_end) {
-                       vma = find_vma(mm, start);
-                       if (!vma || start < vma->vm_start)
+                       vma = vma_lookup(mm, start);
+                       if (!vma)
                                return -ENOMEM;
                }