From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751422AbdH2TO4 (ORCPT ); Tue, 29 Aug 2017 15:14:56 -0400 Received: from mx1.redhat.com ([209.132.183.28]:51708 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751215AbdH2TOz (ORCPT ); Tue, 29 Aug 2017 15:14:55 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 1C402C047B89 Authentication-Results: ext-mx07.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx07.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=jglisse@redhat.com Date: Tue, 29 Aug 2017 15:14:49 -0400 From: Jerome Glisse To: Linus Torvalds Cc: Linux Kernel Mailing List , linux-mm , Bernhard Held , Adam Borowski , Andrea Arcangeli , Radim =?utf-8?B?S3LEjW3DocWZ?= , Wanpeng Li , Paolo Bonzini , Takashi Iwai , Nadav Amit , Mike Galbraith , "Kirill A . Shutemov" , axie , Andrew Morton Subject: Re: [RFC PATCH] mm/rmap: do not call mmu_notifier_invalidate_page() v3 Message-ID: <20170829191449.GE7546@redhat.com> References: <20170829190526.8767-1-jglisse@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.8.3 (2017-05-23) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.31]); Tue, 29 Aug 2017 19:14:55 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 29, 2017 at 12:09:45PM -0700, Linus Torvalds wrote: > On Tue, Aug 29, 2017 at 12:05 PM, Jérôme Glisse wrote: > > Some MMU notifier need to be able to sleep during callback. This was > > broken by c7ab0d2fdc84 ("mm: convert try_to_unmap_one() to use > > page_vma_mapped_walk()"). > > No. No no no. > > Didn't you learn *anything* from the bug? > > You cannot replace "mmu_notifier_invalidate_page()" with > "mmu_notifier_invalidate_range()". > > KVM implements mmu_notifier_invalidate_page(). > > IT DOES NOT IMPLEMENT THAT RANGE CRAP AT ALL. > > So any approach like this is fundamentally garbage. Really. Stop > sending crap. This is exactly tehe same thing that we already reverted > because it was broken shit. Why do you re-send it without actually > fixing the fundamental problems that were pointed out? > Sorry i missed the kvm not implementing the range() only callback so i am gonna respin with start/end. Jérôme