From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bombadil.infradead.org ([65.50.211.133]:35043 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756294AbeAROHm (ORCPT ); Thu, 18 Jan 2018 09:07:42 -0500 Date: Thu, 18 Jan 2018 06:07:39 -0800 From: Matthew Wilcox To: Jan =?iso-8859-1?Q?H=2E_Sch=F6nherr?= Cc: Matthew Wilcox , Ross Zwisler , linux-fsdevel@vger.kernel.org Subject: Re: [PATCH] dax: Release PMD lock even when there is no PMD support in DAX Message-ID: <20180118140739.GA28322@bombadil.infradead.org> References: <20180118133839.20587-1-jschoenh@amazon.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20180118133839.20587-1-jschoenh@amazon.de> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Thu, Jan 18, 2018 at 02:38:39PM +0100, Jan H. Sch�nherr wrote: > The function follow_pte_pmd() can theoretically return after having > acquired a PMD lock, even when DAX was not compiled with > CONFIG_FS_DAX_PMD. I don't think it can. How would a PMD entry get into a DAX VMA if we compiled the kernel without CONFIG_FS_DAX_PMD?