From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1754914AbcBPKQu (ORCPT <rfc822;w@1wt.eu>);
	Tue, 16 Feb 2016 05:16:50 -0500
Received: from mga03.intel.com ([134.134.136.65]:29565 "EHLO mga03.intel.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1754771AbcBPKQr (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Tue, 16 Feb 2016 05:16:47 -0500
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.22,454,1449561600"; 
   d="scan'208";a="747158653"
Date: Tue, 16 Feb 2016 13:16:42 +0300
From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
To: Dave Hansen <dave.hansen@intel.com>
Cc: Hugh Dickins <hughd@google.com>, Andrea Arcangeli <aarcange@redhat.com>,
        Andrew Morton <akpm@linux-foundation.org>,
        Vlastimil Babka <vbabka@suse.cz>, Christoph Lameter <cl@gentwo.org>,
        Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
        Jerome Marchand <jmarchan@redhat.com>, Yang Shi <yang.shi@linaro.org>,
        Sasha Levin <sasha.levin@oracle.com>, linux-kernel@vger.kernel.org,
        linux-mm@kvack.org
Subject: Re: [PATCHv2 19/28] thp: run vma_adjust_trans_huge() outside
 i_mmap_rwsem
Message-ID: <20160216101642.GG46557@black.fi.intel.com>
References: <1455200516-132137-1-git-send-email-kirill.shutemov@linux.intel.com>
 <1455200516-132137-20-git-send-email-kirill.shutemov@linux.intel.com>
 <56BE295A.6060209@intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <56BE295A.6060209@intel.com>
User-Agent: Mutt/1.5.23.1 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Fri, Feb 12, 2016 at 10:50:02AM -0800, Dave Hansen wrote:
> On 02/11/2016 06:21 AM, Kirill A. Shutemov wrote:
> > vma_addjust_trans_huge() splits pmd if it's crossing VMA boundary.
> > During split we munlock the huge page which requires rmap walk.
> > rmap wants to take the lock on its own.
> 
> Which lock are you talking about here?

i_mmap_rwsem. It's in patch subject. I'll update body.

-- 
 Kirill A. Shutemov