Hello. I'm just curious if ufs_vnops.c#rev1.290 fixes this LOR (or not): lock order reversal: 1st 0xcc9d1b00 kqueue (kqueue) @ /usr/src/sys_uvmem_uip.6.2_RELEASE/kern/kern_event.c:1547 2nd 0xc6d6b854 struct mount mtx (struct mount mtx) @ /usr/src/sys_uvmem_uip.6.2_RELEASE/ufs/ufs/ufs_vnops.c:138 KDB: stack backtrace: kdb_backtrace(0,ffffffff,c0a61df0,c0a61ee0,c09ce140,...) at kdb_backtrace+0x29 witness_checkorder(c6d6b854,9,c096683a,8a) at witness_checkorder+0x578 _mtx_lock_flags(c6d6b854,0,c096683a,8a,554,...) at _mtx_lock_flags+0x78 ufs_itimes(cbf6c000,cbf6c000,f78c0a5c,c70019d4,cd225048,...) at ufs_itimes+0x58 ufs_getattr(f78c0a5c) at ufs_getattr+0x1e VOP_GETATTR_APV(c0a09b00,f78c0a5c) at VOP_GETATTR_APV+0x7e filt_vfsread(c70019d4,6) at filt_vfsread+0x6b knote(cd225048,6,1) at knote+0x98 VOP_WRITE_APV(c0a09b00,f78c0bf4) at VOP_WRITE_APV+0x186 vn_write(c934c240,f78c0cbc,cc0b0300,0,c93ed7d0) at vn_write+0x1ea dofilewrite(c93ed7d0,3,c934c240,f78c0cbc,ffffffff,...) at dofilewrite+0x77 kern_writev(c93ed7d0,3,f78c0cbc,8054038,0,...) at kern_writev+0x3b write(c93ed7d0,f78c0d04) at write+0x45 syscall(3b,3b,3b,8054000,28296da0,...) at syscall+0x22f Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (4, FreeBSD ELF32, write), eip = 0x2827232f, esp 0xbfbfd74c, ebp = 0xbfbfd768 --- P.S. I've caught this two times (almost at once) today. -- wbr, pluknet