diff mbox series

[1/1] fixup! mm: fix a crash due to vma_end_read() that should have been removed

Message ID 20250220200208.323769-1-surenb@google.com (mailing list archive)
State New
Headers show
Series [1/1] fixup! mm: fix a crash due to vma_end_read() that should have been removed | expand

Commit Message

Suren Baghdasaryan Feb. 20, 2025, 8:02 p.m. UTC 
Handling a vma lock failure due to vma being detached from under us got
changed but vma_end_read() in that path was left untouched while it should
have been removed. Remove it.

Fixes: 758f7664c3d1 ("mm: replace vm_lock and detached flag with a reference count")
Reported-by: Heiko Carstens <hca@linux.ibm.com>
Closes: https://lore.kernel.org/all/20250220185304.8313A7d-hca@linux.ibm.com/
Signed-off-by: Suren Baghdasaryan <surenb@google.com>
---
 mm/memory.c | 1 -
 1 file changed, 1 deletion(-)


base-commit: f7ed46277aaa8f848f18959ff68469f5186ba87c
diff mbox series

Patch

diff --git a/mm/memory.c b/mm/memory.c
index cacf6d53bdf3..567b45e5d149 100644
--- a/mm/memory.c
+++ b/mm/memory.c
@@ -6496,7 +6496,6 @@  struct vm_area_struct *lock_vma_under_rcu(struct mm_struct *mm,
 	if (IS_ERR_OR_NULL(vma)) {
 		/* Check if the VMA got isolated after we found it */
 		if (PTR_ERR(vma) == -EAGAIN) {
-			vma_end_read(vma);
 			count_vm_vma_lock_event(VMA_LOCK_MISS);
 			/* The area was replaced with another one */
 			goto retry;