Re: kern/59955: kernel diagnostic assertion "rw_lock_held(&map->lock)" failed: file "/home/riastradh/netbsd/11/src/sys/uvm/uvm_map.c", line 1704

["Taylor R Campbell via gnats" <gnats-admin%NetBSD.org@localhost>]

The following reply was made to PR kern/59955; it has been noted by GNATS.

From: Taylor R Campbell <riastradh%NetBSD.org@localhost>
To: gnats-bugs%NetBSD.org@localhost, netbsd-bugs%NetBSD.org@localhost
Cc: chs%NetBSD.org@localhost
Subject: Re: kern/59955: kernel diagnostic assertion "rw_lock_held(&map->lock)" failed: file "/home/riastradh/netbsd/11/src/sys/uvm/uvm_map.c", line 1704
Date: Sun, 1 Feb 2026 20:37:45 +0000

 Actually, just taking the read lock in mm_md_kernacc probably isn't
 enough, because we really need the access to _remain_ allowed while we
 do the uiomove in dev/mm.c.  Can we hold the map lock across uiomove?
 Sounds unlikely.  Can we wire the pages with uvm_vslock or something
 across the uvm_map_checkprot and uiomove?