[Intel-gfx] [PATCH 4/6] mm: Check if mmut notifier callbacks are allowed to fail
Daniel Vetter
daniel.vetter at ffwll.ch
Thu Oct 25 14:35:25 UTC 2018
Just a bit of paranoia, since if we start pushing this deep into
callchains it's hard to spot all.
Signed-off-by: Daniel Vetter <daniel.vetter at 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 82bb1a939c0e..744840e5636e 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
More information about the Intel-gfx
mailing list