Re: uvm locking inconsistency

[Mindaugas Rasiukevicius <rmind%netbsd.org@localhost>]

Matthias Drochner <M.Drochner%fz-juelich.de@localhost> wrote:
> 
> A fresh kernel panics for me with a KASSERT about a lock
> not held - see attachment.
> uvm_pgalloc() was called from amap_cow_now() -- the anon is
> freshly allocated, so the reason for the panic is obvious.
> (and it seems better to relax the check than to acquire the
> lock for no good reason)
> Am I the only one using DIAGNOSTIC kernels?

Well, my diagnostic kernel did not trigger the assert, for some reason..

Anyway, I have committed a fix.

-- 
Mindaugas