Date: Wed, 25 Aug 2021 21:10:29 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 258049] vm_reserv_depopulate panic. Message-ID: <bug-258049-227-52e39n059H@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-258049-227@https.bugs.freebsd.org/bugzilla/> References: <bug-258049-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D258049 Jessica Clarke <jrtc27@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jrtc27@freebsd.org --- Comment #1 from Jessica Clarke <jrtc27@freebsd.org> --- Re observed on amd64, Google has 5 hits (I assume this bug report will shor= tly appear too) for `"vm_reserv_depopulate" "is clear"`, all but one of which a= re just for the code, with the final one being for this 5 year old GitHub Gist https://gist.github.com/nomadlogic/ba58e8fd01267fbf7a2fa4fcee29e2f7 that was for FreeBSD 12.0-CURRENT on amd64 when using the old freebsd-base-graphics tree. Looking at vm_reserv itself, whilst a caller can do stupid things and potentially cause crashes, my initial reading is that this KASSERT should be impossible no matter what the caller is doing. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-258049-227-52e39n059H>