[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170419123051.GA5730@worktop>
Date: Wed, 19 Apr 2017 14:30:51 +0200
From: Peter Zijlstra <peterz@...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>,
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 2/4] Deactivate mmap_sem assert
On Wed, Apr 19, 2017 at 02:18:25PM +0200, Laurent Dufour wrote:
> When mmap_sem will be moved to a range lock, some assertion done in
> the code are no more valid, like the one ensuring mmap_sem is held.
>
Why are they no longer valid?
Powered by blists - more mailing lists