Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp4233210yba; Tue, 7 May 2019 14:37:22 -0700 (PDT) X-Google-Smtp-Source: APXvYqzhVbO2We+QgQ4Nv1GM1ML9cAgaN4T7Vuszyom2DRT0uSd5VhDBS7wqb/JCoR+yZZc4WnV6 X-Received: by 2002:a17:902:e287:: with SMTP id cf7mr43116811plb.217.1557265042747; Tue, 07 May 2019 14:37:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557265042; cv=none; d=google.com; s=arc-20160816; b=wyUR6Nq3f5REJrMa17ziCIgnOhrO8uXF2KYgrXYEWmRimavJiY2Ek5BGveEx5FiIEe aJ/jxxv3HIalipfzxKKADpFuvB9o9V4NAtzWKXqrwKdtNyK79GmO1tOdabiwhD+jxbEU bic0A1x5ly3CiFq34BQTjJ1qGJ5f6EHAvNVNtoYoMTbwRyOmBdqUFcfaL+4n1W0C15Am 3tGoIzz29ns7rugUpMhTUu1soK9MfbZGRxdqDlUuJrugWDE9MkO9rjJ9pIIV2xABmw8Y wD7y2Hf0LroZfIjeoy789DmpC2i06CIycGpHB/9To6gzOy8w91Pqor/g3at53A8QiJne 2Exg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from; bh=led0DBv6u7UXI25sAuz4CP9LBCMQYh8UhwHyrJqvOkg=; b=V3nu7bW1RhK1ouHhqpD3M8RpVSz05pkCOQx/VZbxJzpNU9ZXjHVoEqmTqAHFWlW54Q VPJUcCcjW9uGDquk7XAs9pJyk+Uzp5iBVjWPEVjFp71PXtHReBC4bmp/jryqVrvx01hG e0Hn6677kpohFu4QYEkjXn7zcf8VYymyemLtL4iipqL2cCNecGibpgLQaUjJVLW5lNgo nXUIBjI9Zjf9Lumw9WKkH395ff45bqyqLFI9/VB+iGXlSJztBBxxFZzz/InQ8R7Q41+9 qSd22Eawxi/rk377VXhYZd/2m/3wrP+8vZ6PmxaGX4o3Tq4iD91V1THrnpWA1kPdKg3+ 9ptg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=alibaba.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id n6si600760plk.237.2019.05.07.14.37.06; Tue, 07 May 2019 14:37:22 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=alibaba.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728588AbfEGVfA (ORCPT + 99 others); Tue, 7 May 2019 17:35:00 -0400 Received: from out4437.biz.mail.alibaba.com ([47.88.44.37]:43938 "EHLO out4437.biz.mail.alibaba.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726650AbfEGVfA (ORCPT ); Tue, 7 May 2019 17:35:00 -0400 X-Alimail-AntiSpam: AC=PASS;BC=-1|-1;BR=01201311R201e4;CH=green;DM=||false|;FP=0|-1|-1|-1|0|-1|-1|-1;HT=e01e04420;MF=yang.shi@linux.alibaba.com;NM=1;PH=DS;RN=7;SR=0;TI=SMTPD_---0TR8MvA1_1557264889; Received: from e19h19392.et15sqa.tbsite.net(mailfrom:yang.shi@linux.alibaba.com fp:SMTPD_---0TR8MvA1_1557264889) by smtp.aliyun-inc.com(127.0.0.1); Wed, 08 May 2019 05:34:56 +0800 From: Yang Shi To: jstancek@redhat.com, will.deacon@arm.com, akpm@linux-foundation.org Cc: yang.shi@linux.alibaba.com, stable@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: [PATCH] mm: mmu_gather: remove __tlb_reset_range() for force flush Date: Wed, 8 May 2019 05:34:49 +0800 Message-Id: <1557264889-109594-1-git-send-email-yang.shi@linux.alibaba.com> X-Mailer: git-send-email 1.8.3.1 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org A few new fields were added to mmu_gather to make TLB flush smarter for huge page by telling what level of page table is changed. __tlb_reset_range() is used to reset all these page table state to unchanged, which is called by TLB flush for parallel mapping changes for the same range under non-exclusive lock (i.e. read mmap_sem). Before commit dd2283f2605e ("mm: mmap: zap pages with read mmap_sem in munmap"), MADV_DONTNEED is the only one who may do page zapping in parallel and it doesn't remove page tables. But, the forementioned commit may do munmap() under read mmap_sem and free page tables. This causes a bug [1] reported by Jan Stancek since __tlb_reset_range() may pass the wrong page table state to architecture specific TLB flush operations. So, removing __tlb_reset_range() sounds sane. This may cause more TLB flush for MADV_DONTNEED, but it should be not called very often, hence the impact should be negligible. The original proposed fix came from Jan Stancek who mainly debugged this issue, I just wrapped up everything together. [1] https://lore.kernel.org/linux-mm/342bf1fd-f1bf-ed62-1127-e911b5032274@linux.alibaba.com/T/#m7a2ab6c878d5a256560650e56189cfae4e73217f Reported-by: Jan Stancek Tested-by: Jan Stancek Cc: Will Deacon Cc: stable@vger.kernel.org Signed-off-by: Yang Shi Signed-off-by: Jan Stancek --- mm/mmu_gather.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/mm/mmu_gather.c b/mm/mmu_gather.c index 99740e1..9fd5272 100644 --- a/mm/mmu_gather.c +++ b/mm/mmu_gather.c @@ -249,11 +249,12 @@ void tlb_finish_mmu(struct mmu_gather *tlb, * flush by batching, a thread has stable TLB entry can fail to flush * the TLB by observing pte_none|!pte_dirty, for example so flush TLB * forcefully if we detect parallel PTE batching threads. + * + * munmap() may change mapping under non-excluse lock and also free + * page tables. Do not call __tlb_reset_range() for it. */ - if (mm_tlb_flush_nested(tlb->mm)) { - __tlb_reset_range(tlb); + if (mm_tlb_flush_nested(tlb->mm)) __tlb_adjust_range(tlb, start, end - start); - } tlb_flush_mmu(tlb); -- 1.8.3.1