lang: en

FreeBSD lock order reversal (LOR) #260

ID 260
state unknown
responsible
reported first 2008-09-30
reported last
do you know more? submit update by email
LOR
lock order reversal:
 1st 0xc33e837c syncer (syncer) @ sys/kern/vfs_subr.c:1659
 2nd 0xc3395a90 vfslock (vfslock) @ sys/kern/vfs_subr.c:372
		
KDB: stack backtrace:
db_trace_self_wrapper(c0bbad75,d5157aec,c082ff55,4,c0bb671e,...) at db_trace_self_wrapper+0x26
kdb_backtrace(4,c0bb671e,c0bc4478,c3079fe0,d5157b48,...) at kdb_backtrace+0x29
_witness_debugger(c0bbd62a,c3395a90,c0bc3ed3,c3079fe0,c0bc4478,...) at _witness_debugger+0x25
witness_checkorder(c3395a90,1,c0bc4478,174,0,...) at witness_checkorder+0x810
__lockmgr_args(c3395a90,200100,c3395aac,0,0,...) at __lockmgr_args+0x237
vfs_busy(c3395a90,80200,c0e68380,d1c,c3395a90,...) at vfs_busy+0x1bc
sync_fsync(d5157c7c,c33e8398,c33e8324,d5157c7c,d5157c9c,...) at sync_fsync+0xb5
VOP_FSYNC_APV(c0ca12e0,d5157c7c,c0bc4478,67b,c3279000,...) at VOP_FSYNC_APV+0xa5
sync_vnode(c0e68470,c0e6845c,3e8,6aa,4e20,...) at sync_vnode+0x168
sched_sync(0,d5157d38,c0bb4070,322,c311a7d4,...) at sched_sync+0x273
fork_exit(c087a2d0,0,d5157d38) at fork_exit+0xb8
fork_trampoline() at fork_trampoline+0x8
--- trap 0, eip = 0, esp = 0xd5157d70, ebp = 0 ---
		
comments/references