[4/6] mm: Check if mmut notifier callbacks are allowed to fail
diff mbox series

Message ID 20181025143527.8575-5-daniel.vetter@ffwll.ch
State New
Headers show
Series
  • attempts at catching mmu_notifer deadlocks
Related show

Commit Message

Daniel Vetter Oct. 25, 2018, 2:35 p.m. UTC
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@intel.com>
---
 mm/mmu_notifier.c | 2 ++
 1 file changed, 2 insertions(+)

Patch
diff mbox series

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;
 			}
 		}