Re: [PATCH] mm/mlock: Use vma_lookup() instead of find_vma()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Miaohe Lin <linmiaohe@xxxxxxxxxx>
Subject: Re: [PATCH] mm/mlock: Use vma_lookup() instead of find_vma()
From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
Date: Mon, 14 Mar 2022 16:16:54 +0000
Cc: akpm@xxxxxxxxxxxxxxxxxxxx, hughd@xxxxxxxxxx, linux-mm@xxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to: <20220314151728.20800-1-linmiaohe@huawei.com>
References: <20220314151728.20800-1-linmiaohe@huawei.com>

On Mon, Mar 14, 2022 at 11:17:28PM +0800, Miaohe Lin wrote:
> Using vma_lookup() verifies the start is contained in the found vma. This
> results in easier to read the code.

This conflicts with the maple tree.

Follow-Ups:
- Re: [PATCH] mm/mlock: Use vma_lookup() instead of find_vma()
  - From: Miaohe Lin

References:
- [PATCH] mm/mlock: Use vma_lookup() instead of find_vma()
  - From: Miaohe Lin

Prev by Date: Re: [mm/slub] ae107fa919: BUG:unable_to_handle_page_fault_for_address
Next by Date: Re: [PATCH] mm/mempolicy: fix potential mpol_new leak in shared_policy_replace
Previous by thread: [PATCH] mm/mlock: Use vma_lookup() instead of find_vma()
Next by thread: Re: [PATCH] mm/mlock: Use vma_lookup() instead of find_vma()
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Bugtraq] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API]

Powered by Linux