Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp3925394ybl; Mon, 26 Aug 2019 02:43:55 -0700 (PDT) X-Google-Smtp-Source: APXvYqxU/GJZ6IP/bSQftFOPYwpAcQM1jsVRFO6q95QjBW9kD0IYVSHc5oNhwXyuYsq9WljRLB7e X-Received: by 2002:a17:902:bb94:: with SMTP id m20mr17769490pls.336.1566812634953; Mon, 26 Aug 2019 02:43:54 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566812634; cv=none; d=google.com; s=arc-20160816; b=b/QnDyA2hFE9vGIP1HFRDJL+ZpQdvsjeZNeMVMC9XyVwwsjf6JbnQB3MhaBsqQ9CZ4 8mZPHWo6s2NRBOmriBDzpU7a6rS/G6GT30zVFnNxymuXsLeWsnGZT9eQ0qDoQ3Qd7hOo QbojqYhfOpJ5ZhJyTDgRZTfNsXMo5X8ChsVqKEos8NykgW198cDrfnnQOVEPi33lCv4+ 2Mw4cSTsMqReQIruWtHapkhnM7hmuf+DVT5075HYg2/hCvJi1JxXOQmKdrL03UA+xdRe q7OQmCT0GJbFEjgqxY9pcy9IcpLwoTgE6jutBWdLQJFe2SYp3X46R5MmBOJmcHvVOJK1 369Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:message-id:date :subject:cc:to:from; bh=VI+qVkdjw0W6VljvvWVDZ26jDg4MnFar8Ewr5lUeadg=; b=G3YEEQ2Qtd28bXnZxBXjUR1EY2Yl+TdeFegN5q4wjAiYnZzOEv/2G+Q4t10GESvJzs uoHcdpbOkWJqxuDNPpNyaqmOmJdZHeevH+JxI8Ec16cwoki+82T+iwuXOorPCwgv+VIp xDUX99iRmWodryv0JaUULpHUQEHJWXoZGl8wzcASOv+xAKftKaDwJYwvtXaKz6NoPP7T pwZgBz+a+5y2XQY7VnT7CE0Ny5+t3gw/QqZoUPoHsXE6xSeCY7ipjhnRFCrDTymfShLO sjURcXFwGmsteE0yuTkA+s9t6Wk1iTiq+JDqYAJLwdgr6v1boNOp6RSTmTFHKm1v6d5v NuoA== 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=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h37si9138336pjb.106.2019.08.26.02.43.40; Mon, 26 Aug 2019 02:43:54 -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=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730100AbfHZHbp (ORCPT + 99 others); Mon, 26 Aug 2019 03:31:45 -0400 Received: from mga04.intel.com ([192.55.52.120]:47284 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726896AbfHZHbo (ORCPT ); Mon, 26 Aug 2019 03:31:44 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Aug 2019 00:31:44 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,431,1559545200"; d="scan'208";a="196992425" Received: from richard.sh.intel.com (HELO localhost) ([10.239.159.54]) by fmsmga001.fm.intel.com with ESMTP; 26 Aug 2019 00:31:43 -0700 From: Wei Yang To: akpm@linux-foundation.org, vbabka@suse.cz, kirill.shutemov@linux.intel.com, yang.shi@linux.alibaba.com Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, Wei Yang Subject: [PATCH 1/2] mm/mmap.c: update *next* gap after itself Date: Mon, 26 Aug 2019 15:31:05 +0800 Message-Id: <20190826073106.29971-2-richardw.yang@linux.intel.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20190826073106.29971-1-richardw.yang@linux.intel.com> References: <20190826073106.29971-1-richardw.yang@linux.intel.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Since we link a vma to the leaf of a rb_tree, *next* must be a parent of vma if *next* is not NULL. This means if we update *next* gap first, it will be re-update again if vma's gap is bigger. For example, we have a vma tree like this: a [0x9000, 0x10000] / \ b c [0x8000, 0x9000] [0x10000, 0x11000] The gap for each node is: a's gap = 0x8000 b's gap = 0x8000 c's gap = 0x0 Now we want to insert d [0x6000, 0x7000], then the tree look like this: a [0x9000, 0x10000] / \ b c [0x8000, 0x9000] [0x10000, 0x11000] / d [0x6000, 0x7000] b is the *next* of d. If we update b's gap first, it would be 0x1000 and propagate to a. And then when update d's gap, which is 0x6000 and propagate through b to a again. If we update d's gap first, the un-consistent gap 0x1000 will not be propagated. Signed-off-by: Wei Yang --- mm/mmap.c | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/mm/mmap.c b/mm/mmap.c index aa66753b175e..672ad7dc6b3c 100644 --- a/mm/mmap.c +++ b/mm/mmap.c @@ -587,12 +587,6 @@ static unsigned long count_vma_pages_range(struct mm_struct *mm, void __vma_link_rb(struct mm_struct *mm, struct vm_area_struct *vma, struct rb_node **rb_link, struct rb_node *rb_parent) { - /* Update tracking information for the gap following the new vma. */ - if (vma->vm_next) - vma_gap_update(vma->vm_next); - else - mm->highest_vm_end = vm_end_gap(vma); - /* * vma->vm_prev wasn't known when we followed the rbtree to find the * correct insertion point for that vma. As a result, we could not @@ -605,6 +599,13 @@ void __vma_link_rb(struct mm_struct *mm, struct vm_area_struct *vma, rb_link_node(&vma->vm_rb, rb_parent, rb_link); vma->rb_subtree_gap = 0; vma_gap_update(vma); + + /* Update tracking information for the gap following the new vma. */ + if (vma->vm_next) + vma_gap_update(vma->vm_next); + else + mm->highest_vm_end = vm_end_gap(vma); + vma_rb_insert(vma, &mm->mm_rb); } -- 2.17.1