Just a bit of paranoia, since if we start pushing this deep into
callchains it's hard to spot all places where an mmu notifier
implementation might fail when it's not allowed to.
Cc: Andrew Morton <a...@linux-foundation.org>
Cc: Michal Hocko <mho...@suse.com>
Cc: "Christian König" <christian.koe...@amd.com>
Cc: David Rientjes <rient...@google.com>
Cc: Daniel Vetter <daniel.vet...@ffwll.ch>
Cc: "Jérôme Glisse" <jgli...@redhat.com>
Cc: linux...@kvack.org
Cc: Paolo Bonzini <pbonz...@redhat.com>
Signed-off-by: Daniel Vetter <daniel.vet...@intel.com>
---
mm/mmu_notifier.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/mm/mmu_notifier.c b/mm/mmu_notifier.c
index 5119ff846769..59e102589a25 100644
--- a/mm/mmu_notifier.c
+++ b/mm/mmu_notifier.c
@@ -190,6 +190,8 @@ int __mmu_notifier_invalidate_range_start(struct mm_struct
*mm,
pr_info("%pS callback failed with %d in
%sblockable context.\n",
mn->ops->invalidate_range_start, _ret,
!blockable ? "non-" : "");
+ WARN(blockable,"%pS callback failure not
allowed\n",
+ mn->ops->invalidate_range_start);
ret = _ret;
}
}
--
2.19.1
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
