We want to teach lockdep that mmu notifiers can be called from direct reclaim paths, since on many CI systems load might never reach that level (e.g. when just running fuzzer or small functional tests). I've put the annotation into mmu_notifier_register since only when we have mmu notifiers registered is there any point in teaching lockdep about them. Also, we already have a kmalloc(, GFP_KERNEL), so this is safe.
Unified · Split
| @@ -243,6 +243,13 @@ int __mmu_notifier_register(struct mmu_notifier *mn, struct mm_struct *mm) · 242 unmodified lines | ||
| 243 | 243 | lockdep_assert_held_write(&mm->mmap_sem); |
| 244 | 244 | BUG_ON(atomic_read(&mm->mm_users) <= 0); |
| 245 | 245 | |
| 246 | + if (IS_ENABLED(CONFIG_LOCKDEP)) { | |
| 247 | + fs_reclaim_acquire(GFP_KERNEL); | |
| 248 | + lock_map_acquire(&__mmu_notifier_invalidate_range_start_map); | |
| 249 | + lock_map_release(&__mmu_notifier_invalidate_range_start_map); | |
| 250 | + fs_reclaim_release(GFP_KERNEL); | |
| 251 | + } | |
| 252 | + | |
| 246 | 253 | mn->mm = mm; |
| 247 | 254 | mn->users = 1; |
| 248 | 255 | |