On Sat, Dec 11, 2021 at 01:13:32AM +0100, Alexander Bluhm wrote: > I have turned on witness during a full regress run on amd64.
Got another one, this time during make release. I will try to keep witness active on one of my regress/build/release machines. bluhm witness: lock order reversal: 1st 0xfffffd8867790768 vmmaplk (&map->lock) 2nd 0xfffffd87bb1d00a8 inode (&ip->i_lock) lock order "&ip->i_lock"(rrwlock) -> "&map->lock"(rwlock) first seen at: #0 rw_enter_read+0x38 #1 uvmfault_lookup+0x8a #2 uvm_fault_check+0x32 #3 uvm_fault+0xfc #4 kpageflttrap+0x12c #5 kerntrap+0x91 #6 alltraps_kern_meltdown+0x7b #7 copyout+0x53 #8 ffs_read+0x1f6 #9 VOP_READ+0x41 #10 vn_rdwr+0xa1 #11 vmcmd_map_readvn+0xa0 #12 exec_process_vmcmds+0x88 #13 sys_execve+0x738 #14 syscall+0x374 #15 Xsyscall+0x128 lock order "&map->lock"(rwlock) -> "&ip->i_lock"(rrwlock) first seen at: #0 rw_enter+0x68 #1 rrw_enter+0x56 #2 VOP_LOCK+0x5b #3 vn_lock+0xad #4 vn_rdwr+0x7f #5 vndstrategy+0x2ca #6 physio+0x237 #7 spec_read+0xa7 #8 VOP_READ+0x41 #9 vn_read+0xa6 #10 dofilereadv+0x146 #11 sys_read+0x51 #12 syscall+0x374 #13 Xsyscall+0x128
