mm-mmu_notifier-fix-mmget-assert-in-__mmu_interval_notifier_insert.patch removed from -mm tree
The patch titled
Subject: mm/mmu_notifier: fix mmget() assert in __mmu_interval_notifier_insert
has been removed from the -mm tree. Its filename was
mm-mmu_notifier-fix-mmget-assert-in-__mmu_interval_notifier_insert.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Jann Horn <[email protected]>
Subject: mm/mmu_notifier: fix mmget() assert in __mmu_interval_notifier_insert
The comment talks about having to hold mmget() (which means mm_users), but the actual check is on mm_count (which would be mmgrab()).
Given that MMU notifiers are torn down in mmput() -> __mmput() -> exit_mmap() -> mmu_notifier_release(), I believe that the comment is correct and the check should be on mm->mm_users. Fix it up accordingly.
---
mm/mmu_notifier.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
mm/mmu_notifier.c renamed from mm/mmu_notifier.c~mm-mmu_notifier-fix-mmget-assert-in-__mmu_interval_notifier_insert +1 -1
@@ -913,7 +913,7 @@ static int __mmu_interval_notifier_inserreturn -EOVERFLOW ;/* Must call with a mmget() held */ -if (WARN_ON (atomic_read (&mm->mm_count) <=0 )) +if (WARN_ON (atomic_read (&mm->mm_users) <=0 ))return -EINVAL ;/* pairs with mmdrop in mmu_interval_notifier_remove() */
_
Patches currently in -mm which might be from [email protected] are
mm-gup_benchmark-take-the-mmap-lock-around-gup.patch binfmt_elf-take-the-mmap-lock-around-find_extend_vma.patch mmap-locking-api-dont-check-locking-if-the-mm-isnt-live-yet.patch mm-gup-assert-that-the-mmap-lock-is-held-in-__get_user_pages.patch