linux-kernel - Re: [PATCH] mm/mlock: Use vma_lookup() instead of find

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <b2dc4e8a-be8f-88e4-040a-91a6d033ab6d@huawei.com>
Date:   Tue, 15 Mar 2022 20:24:04 +0800
From:   Miaohe Lin <linmiaohe@...wei.com>
To:     Matthew Wilcox <willy@...radead.org>
CC:     <akpm@...ux-foundation.org>, <hughd@...gle.com>,
        <linux-mm@...ck.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] mm/mlock: Use vma_lookup() instead of find_vma()

On 2022/3/15 0:16, Matthew Wilcox wrote:
> 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.

IIUC, maple tree is the implementation detail of the vma and this patch
should not be conflict with it. But there might be some trival conflict.
Am I supposed to delay this patch until the maple tree's work is done?

Thanks.

> 
> .
>