linux-kernel - Re: [RFC 0/4] Replace mmap

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: <20170420133338.GC27790@bombadil.infradead.org>
Date:   Thu, 20 Apr 2017 06:33:38 -0700
From:   Matthew Wilcox <willy@...radead.org>
To:     Laurent Dufour <ldufour@...ux.vnet.ibm.com>
Cc:     linux-mm@...ck.org, Davidlohr Bueso <dave@...olabs.net>,
        akpm@...ux-foundation.org, Jan Kara <jack@...e.cz>,
        "Kirill A . Shutemov" <kirill@...temov.name>,
        Michal Hocko <mhocko@...nel.org>,
        Peter Zijlstra <peterz@...radead.org>,
        Mel Gorman <mgorman@...hsingularity.net>,
        haren@...ux.vnet.ibm.com, aneesh.kumar@...ux.vnet.ibm.com,
        khandual@...ux.vnet.ibm.com, Paul.McKenney@...ibm.com,
        linux-kernel@...r.kernel.org
Subject: Re: [RFC 0/4] Replace mmap_sem by a range lock

On Wed, Apr 19, 2017 at 02:18:23PM +0200, Laurent Dufour wrote:
> Following the series pushed by Davidlohr Bueso based on the Jan Kara's
> work [1] which introduces range locks, this series implements the
> first step of the attempt to replace the mmap_sem by a range lock.

Have you previously documented attempts to replace the mmap_sem by an
existing lock type before introducing a new (and frankly weird) lock?
My initial question is "Why not use RCU for this?" -- the rxrpc code
uses an rbtree protected by RCU.