lock order reversal: 1st 0xffffff0078c6b648 filedesc structure (filedesc structure) @ /usr/src/sys/kern/sys_generic.c:1211 2nd 0xffffff0078b73620 ufs (ufs) @ /usr/src/sys/kern/vfs_vnops.c:863 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a _witness_debugger() at _witness_debugger+0x2e witness_checkorder() at witness_checkorder+0x81e __lockmgr_args() at __lockmgr_args+0xcf3 ffs_lock() at ffs_lock+0x8c VOP_LOCK1_APV() at VOP_LOCK1_APV+0x9b _vn_lock() at _vn_lock+0x47 vn_poll() at vn_poll+0x64 poll() at poll+0x1b8 syscall() at syscall+0x1af Xfast_syscall() at Xfast_syscall+0xe1 --- syscall (209, FreeBSD ELF64, poll), rip = 0x804878e6c, rsp = 0x7fffffff7a88, rbp = 0x38 --- How-To-Repeat: GENERIC kernel, only devfs and UFS2 filesystems mounted via /dev/ad* (/ , /var, /tmp, /usr)
Responsible Changed From-To: freebsd-bugs->freebsd-fs Over to maintainer(s).
I would actually expect this to be the correct order for these two locks. Can you capture the output of the 'debug.witness.fullgraph' sysctl to a file? -- John Baldwin
2009/7/27 John Baldwin <jhb@freebsd.org>: > I would actually expect this to be the correct order for these two locks.= =A0Can > you capture the output of the 'debug.witness.fullgraph' sysctl to a file? > Yes, see attachment. I'm still running the same 8.0-BETA2.
For bugs matching the following criteria: Status: In Progress Changed: (is less than) 2014-06-01 Reset to default assignee and clear in-progress tags. Mail being skipped