From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bombadil.infradead.org ([198.137.202.133]:51882 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727436AbfACOgt (ORCPT ); Thu, 3 Jan 2019 09:36:49 -0500 Date: Thu, 3 Jan 2019 06:36:47 -0800 From: Matthew Wilcox Subject: Re: [PATCH] Initialise mmu_notifier_range correctly Message-ID: <20190103143647.GP6310@bombadil.infradead.org> References: <20190103002126.GM6310@bombadil.infradead.org> <20190103143116.GB3395@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190103143116.GB3395@redhat.com> Sender: linux-xfs-owner@vger.kernel.org List-ID: List-Id: xfs To: Jerome Glisse Cc: Andrew Morton , linux-mm@kvack.org, linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org, Christian =?iso-8859-1?Q?K=F6nig?= , Jan Kara On Thu, Jan 03, 2019 at 09:31:16AM -0500, Jerome Glisse wrote: > On Wed, Jan 02, 2019 at 04:21:26PM -0800, Matthew Wilcox wrote: > > > > One of the paths in follow_pte_pmd() initialised the mmu_notifier_range > > incorrectly. > > > > Signed-off-by: Matthew Wilcox > > Fixes: ac46d4f3c432 ("mm/mmu_notifier: use structure for invalidate_range_start/end calls v2") > > Tested-by: Dave Chinner > > Actually now that i have read the code again this is not ok to > do so. The caller of follow_pte_pmd() will call range_init and > follow pmd will only update the range address. So existing code > is ok. The only caller of follow_pte_pmd() does not call range_init() because it doesn't know the address. That's the point of follow_pte_pmd(). > I know this is kind of ugly but i do not see a way around that > uglyness. You wrote the code ...