From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762552AbdDSMbD (ORCPT ); Wed, 19 Apr 2017 08:31:03 -0400 Received: from bombadil.infradead.org ([65.50.211.133]:50462 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1762056AbdDSMbB (ORCPT ); Wed, 19 Apr 2017 08:31:01 -0400 Date: Wed, 19 Apr 2017 14:30:51 +0200 From: Peter Zijlstra To: Laurent Dufour Cc: linux-mm@kvack.org, Davidlohr Bueso , akpm@linux-foundation.org, Jan Kara , "Kirill A . Shutemov" , Michal Hocko , Mel Gorman , haren@linux.vnet.ibm.com, aneesh.kumar@linux.vnet.ibm.com, khandual@linux.vnet.ibm.com, Paul.McKenney@us.ibm.com, linux-kernel@vger.kernel.org Subject: Re: [RFC 2/4] Deactivate mmap_sem assert Message-ID: <20170419123051.GA5730@worktop> References: <582009a3f9459de3d8def1e76db46e815ea6153c.1492595897.git.ldufour@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <582009a3f9459de3d8def1e76db46e815ea6153c.1492595897.git.ldufour@linux.vnet.ibm.com> User-Agent: Mutt/1.5.22.1 (2013-10-16) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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? From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-it0-f70.google.com (mail-it0-f70.google.com [209.85.214.70]) by kanga.kvack.org (Postfix) with ESMTP id ED6E52806D8 for ; Wed, 19 Apr 2017 08:30:56 -0400 (EDT) Received: by mail-it0-f70.google.com with SMTP id 70so9218354ita.22 for ; Wed, 19 Apr 2017 05:30:56 -0700 (PDT) Received: from bombadil.infradead.org (bombadil.infradead.org. [65.50.211.133]) by mx.google.com with ESMTPS id n75si2515232pfi.284.2017.04.19.05.30.55 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 19 Apr 2017 05:30:56 -0700 (PDT) Date: Wed, 19 Apr 2017 14:30:51 +0200 From: Peter Zijlstra Subject: Re: [RFC 2/4] Deactivate mmap_sem assert Message-ID: <20170419123051.GA5730@worktop> References: <582009a3f9459de3d8def1e76db46e815ea6153c.1492595897.git.ldufour@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <582009a3f9459de3d8def1e76db46e815ea6153c.1492595897.git.ldufour@linux.vnet.ibm.com> Sender: owner-linux-mm@kvack.org List-ID: To: Laurent Dufour Cc: linux-mm@kvack.org, Davidlohr Bueso , akpm@linux-foundation.org, Jan Kara , "Kirill A . Shutemov" , Michal Hocko , Mel Gorman , haren@linux.vnet.ibm.com, aneesh.kumar@linux.vnet.ibm.com, khandual@linux.vnet.ibm.com, Paul.McKenney@us.ibm.com, linux-kernel@vger.kernel.org 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? -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org