Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp3740925ybl; Tue, 20 Aug 2019 01:21:05 -0700 (PDT) X-Google-Smtp-Source: APXvYqwBwVVfxJFcfYYebKmoYhptYUKEaHh3+ToQF63BGuDF21CJPHZa727m3s64LnaMGKOsp4vl X-Received: by 2002:a17:90a:b908:: with SMTP id p8mr24841221pjr.65.1566289265748; Tue, 20 Aug 2019 01:21:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566289265; cv=none; d=google.com; s=arc-20160816; b=JOOZjRZLetX3dLlAuBuOC9QFUTuoUL0UzJl7rhYmHsSSZh2QeaE0I9ej2OKMq+LvV3 C5iaZk4d0I8Gb82QkbpvGUtLWt702kvvLFcC7xy5myUp1QuvY+5DFOga55bYsJYrnurL CuaEZCTFyWYzUGzb4OK+/DFKUsd+ykYokWFU8W9bs+BTJei454NQAKuGXA960QpBWq4s KdWZaIVZxDc6a66QHfGfdYs8nAWP4OgbCDOkkZUERdmfmdnXJU5zgy0pwvwAcmeWUXQt aWLW7v09da5Xe7SlkcpMWsoc0ZFQOlUTamGgqJVLIrYN+QtBBCKEFYDg/W5KqFSTrf5s fb0Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=wgia7qPSXicnYInuL6+gfr2cdFlvKPNwuVbgz5GenZE=; b=lJEouSDiaoNA7YooOZwbKZDGUF9gMeq1y3VWLl7VpvmwxRU9PzEcKTcKwEhgZu0ZhC Y9XSf6ER64vJSrgXDGnjeaaWz5BDE/JWP7Sq0aVkgHiogs5tj5+byfaSEMUthtt66f9I xhVRpmqxjnKPhcs4c7/Q9PmED0As8yl7HgN+rQuctdqS2mXICuCurYjE1ygKOB9F5TIM m8KbQTaP2hPcjmW2ta7llgLdAamIPBZyV4O5w2hTACOT9PesGtKNLJBWw4Lg0MuyRILK M+PDF/ajPotQ836KcNt3jyyepbi794JKsrZeFDhk3mTSIh2iND3rLCK6dNYn8yvTNPXL AR2g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ffwll.ch header.s=google header.b=YWxeLKHf; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t184si11565464pgd.211.2019.08.20.01.20.50; Tue, 20 Aug 2019 01:21:05 -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; dkim=pass header.i=@ffwll.ch header.s=google header.b=YWxeLKHf; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729470AbfHTITN (ORCPT + 99 others); Tue, 20 Aug 2019 04:19:13 -0400 Received: from mail-ed1-f66.google.com ([209.85.208.66]:42837 "EHLO mail-ed1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729378AbfHTITL (ORCPT ); Tue, 20 Aug 2019 04:19:11 -0400 Received: by mail-ed1-f66.google.com with SMTP id m44so5342135edd.9 for ; Tue, 20 Aug 2019 01:19:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ffwll.ch; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=wgia7qPSXicnYInuL6+gfr2cdFlvKPNwuVbgz5GenZE=; b=YWxeLKHfVQ6n9wGxXuRJAn+g9qtmHMwaPzmYfWe8BYeYvBhhpUOFVNbgUl+9qLpP7T PHmTFDTMVPwsO/1+PqoKETqfMC0QoEs4IGQgsATXmRfGgRNSHR4/V73LAd/yZFEVWK1y s1kPTUoWam517FLtcOhvQSucIJxk+akolMA3M= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=wgia7qPSXicnYInuL6+gfr2cdFlvKPNwuVbgz5GenZE=; b=gwqIzxpNOhpZuqvBqYLXhpcUbH7AuHbv2Prd4NSZbF/5sBTap+8YOy9dpWAj0+ntwk n+plzRYn5Lgp3ll716XyxChze3g9q/7drElGXww4s0mcO/CJW1cmsEkl9cH5rgWRBxbI 6yQFwCDIuG6+Wr7mAjl1GHcUkwy6GZ3DYcc/oGu381YuitmG70gnfXfwxhQgS5Rc+V4t KmNvQoFceC0ZFttYXJX5jL74KfwssvqB6mPA3ypaYITYgZZ8usmgHga0ynWjKVZk3Kcr mCiEiMAKpXqgB+5hULi1Vs/15uw25aYrBMYCkzIbvt9Haug/pewUjt+vgeiLz6ToScA9 yfzw== X-Gm-Message-State: APjAAAUVo3Lo1B5lCDlxWlXt2h2+OeJYvE3BqUx/F5PY1luUMZ8JlQ4X FjyyoLMUgNbReMnVwx4+YA8x/NgZ0sOAnw== X-Received: by 2002:aa7:d813:: with SMTP id v19mr29744820edq.45.1566289149643; Tue, 20 Aug 2019 01:19:09 -0700 (PDT) Received: from phenom.ffwll.local ([2a02:168:569e:0:3106:d637:d723:e855]) by smtp.gmail.com with ESMTPSA id fj15sm2469623ejb.78.2019.08.20.01.19.08 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 20 Aug 2019 01:19:08 -0700 (PDT) From: Daniel Vetter To: LKML Cc: Linux MM , DRI Development , Intel Graphics Development , Daniel Vetter , Jason Gunthorpe , Chris Wilson , Andrew Morton , David Rientjes , =?UTF-8?q?J=C3=A9r=C3=B4me=20Glisse?= , Michal Hocko , =?UTF-8?q?Christian=20K=C3=B6nig?= , Greg Kroah-Hartman , Mike Rapoport , Daniel Vetter Subject: [PATCH 1/4] mm, notifier: Add a lockdep map for invalidate_range_start/end Date: Tue, 20 Aug 2019 10:18:59 +0200 Message-Id: <20190820081902.24815-2-daniel.vetter@ffwll.ch> X-Mailer: git-send-email 2.23.0.rc1 In-Reply-To: <20190820081902.24815-1-daniel.vetter@ffwll.ch> References: <20190820081902.24815-1-daniel.vetter@ffwll.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This is a similar idea to the fs_reclaim fake lockdep lock. It's fairly easy to provoke a specific notifier to be run on a specific range: Just prep it, and then munmap() it. A bit harder, but still doable, is to provoke the mmu notifiers for all the various callchains that might lead to them. But both at the same time is really hard to reliable hit, especially when you want to exercise paths like direct reclaim or compaction, where it's not easy to control what exactly will be unmapped. By introducing a lockdep map to tie them all together we allow lockdep to see a lot more dependencies, without having to actually hit them in a single challchain while testing. On Jason's suggestion this is is rolled out for both invalidate_range_start and invalidate_range_end. They both have the same calling context, hence we can share the same lockdep map. Note that the annotation for invalidate_ranage_start is outside of the mm_has_notifiers(), to make sure lockdep is informed about all paths leading to this context irrespective of whether mmu notifiers are present for a given context. We don't do that on the invalidate_range_end side to avoid paying the overhead twice, there the lockdep annotation is pushed down behind the mm_has_notifiers() check. v2: Use lock_map_acquire/release() like fs_reclaim, to avoid confusion with this being a real mutex (Chris Wilson). v3: Rebase on top of Glisse's arg rework. v4: Also annotate invalidate_range_end (Jason Gunthorpe) Also annotate invalidate_range_start_nonblock, I somehow missed that one in the first version. Cc: Jason Gunthorpe Cc: Chris Wilson Cc: Andrew Morton Cc: David Rientjes Cc: "Jérôme Glisse" Cc: Michal Hocko Cc: "Christian König" Cc: Greg Kroah-Hartman Cc: Daniel Vetter Cc: Mike Rapoport Cc: linux-mm@kvack.org Signed-off-by: Daniel Vetter --- include/linux/mmu_notifier.h | 8 ++++++++ mm/mmu_notifier.c | 9 +++++++++ 2 files changed, 17 insertions(+) diff --git a/include/linux/mmu_notifier.h b/include/linux/mmu_notifier.h index b6c004bd9f6a..39a86b77a939 100644 --- a/include/linux/mmu_notifier.h +++ b/include/linux/mmu_notifier.h @@ -42,6 +42,10 @@ enum mmu_notifier_event { #ifdef CONFIG_MMU_NOTIFIER +#ifdef CONFIG_LOCKDEP +extern struct lockdep_map __mmu_notifier_invalidate_range_start_map; +#endif + /* * The mmu notifier_mm structure is allocated and installed in * mm->mmu_notifier_mm inside the mm_take_all_locks() protected @@ -310,19 +314,23 @@ static inline void mmu_notifier_change_pte(struct mm_struct *mm, static inline void mmu_notifier_invalidate_range_start(struct mmu_notifier_range *range) { + lock_map_acquire(&__mmu_notifier_invalidate_range_start_map); if (mm_has_notifiers(range->mm)) { range->flags |= MMU_NOTIFIER_RANGE_BLOCKABLE; __mmu_notifier_invalidate_range_start(range); } + lock_map_release(&__mmu_notifier_invalidate_range_start_map); } static inline int mmu_notifier_invalidate_range_start_nonblock(struct mmu_notifier_range *range) { + lock_map_acquire(&__mmu_notifier_invalidate_range_start_map); if (mm_has_notifiers(range->mm)) { range->flags &= ~MMU_NOTIFIER_RANGE_BLOCKABLE; return __mmu_notifier_invalidate_range_start(range); } + lock_map_release(&__mmu_notifier_invalidate_range_start_map); return 0; } diff --git a/mm/mmu_notifier.c b/mm/mmu_notifier.c index 16f1cbc775d0..d12e3079e7a4 100644 --- a/mm/mmu_notifier.c +++ b/mm/mmu_notifier.c @@ -21,6 +21,13 @@ /* global SRCU for all MMs */ DEFINE_STATIC_SRCU(srcu); +#ifdef CONFIG_LOCKDEP +struct lockdep_map __mmu_notifier_invalidate_range_start_map = { + .name = "mmu_notifier_invalidate_range_start" +}; +EXPORT_SYMBOL_GPL(__mmu_notifier_invalidate_range_start_map); +#endif + /* * This function allows mmu_notifier::release callback to delay a call to * a function that will free appropriate resources. The function must be @@ -197,6 +204,7 @@ void __mmu_notifier_invalidate_range_end(struct mmu_notifier_range *range, struct mmu_notifier *mn; int id; + lock_map_acquire(&__mmu_notifier_invalidate_range_start_map); id = srcu_read_lock(&srcu); hlist_for_each_entry_rcu(mn, &range->mm->mmu_notifier_mm->list, hlist) { /* @@ -220,6 +228,7 @@ void __mmu_notifier_invalidate_range_end(struct mmu_notifier_range *range, mn->ops->invalidate_range_end(mn, range); } srcu_read_unlock(&srcu, id); + lock_map_release(&__mmu_notifier_invalidate_range_start_map); } EXPORT_SYMBOL_GPL(__mmu_notifier_invalidate_range_end); -- 2.23.0.rc1