From 178ec26e827162da7a14c0f0a4a44bde532844e5 Mon Sep 17 00:00:00 2001 From: jhb Date: Fri, 29 Apr 2016 17:35:28 +0000 Subject: [PATCH] Don't require write locks on the VM object for vm_page_prev/next. Reviewed by: kib Sponsored by: Chelsio Communications --- sys/vm/vm_page.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sys/vm/vm_page.c b/sys/vm/vm_page.c index 0d2b92e2f80c..2f3b17fb56a9 100644 --- a/sys/vm/vm_page.c +++ b/sys/vm/vm_page.c @@ -1283,7 +1283,7 @@ vm_page_next(vm_page_t m) { vm_page_t next; - VM_OBJECT_ASSERT_WLOCKED(m->object); + VM_OBJECT_ASSERT_LOCKED(m->object); if ((next = TAILQ_NEXT(m, listq)) != NULL && next->pindex != m->pindex + 1) next = NULL; @@ -1301,7 +1301,7 @@ vm_page_prev(vm_page_t m) { vm_page_t prev; - VM_OBJECT_ASSERT_WLOCKED(m->object); + VM_OBJECT_ASSERT_LOCKED(m->object); if ((prev = TAILQ_PREV(m, pglist, listq)) != NULL && prev->pindex != m->pindex - 1) prev = NULL;