Re: panic under FUSE: System call write returning with 1 locks held

On Sun, 11.11.2007 at 10:53:44 +0100, Ulrich Spoerlein wrote:
> I can read from NTFS via FUSE just fine, writing is also no problem if
> I'm using 'cp -pr', but since I want to copy selectively I'm using
> 'find | cpio -dump', this panics the box after a few seconds.
> 
> panic: lockmgr: locking against myself
> KDB: stack backtrace:
> db_trace_self_wrapper(c071561a,cf349ae8,c0537d2a,c07138c3,c077e480,...) at db_trace_self_wrapper+0x26
> kdb_backtrace(c07138c3,c077e480,c0711f62,cf349af4,cf349af4,...) at kdb_backtrace+0x29
> panic(c0711f62,c073f0a0,c266b3b8,c0767fe0,c266b330,...) at panic+0xaa
> _lockmgr(c266b168,3002,c266b198,c255f840,c071a143,...) at _lockmgr+0x432
> vop_stdlock(cf349b84,c05a41f1,1002,c266b110,cf349ba8,...) at vop_stdlock+0x40
> VOP_LOCK1_APV(c2380ba0,cf349b84,cf349ba8,c05bf022,c2380ba0,...) at VOP_LOCK1_APV+0x46
> _vn_lock(c266b110,1002,c255f840,c071a143,a6c,...) at _vn_lock+0x16f
> setfown(0,4,cf349c70,c2634550,c255f840,...) at setfown+0x9c
> fchown(c255f840,cf349cfc,c,86,55349d,...) at fchown+0x134
> syscall(cf349d38) at syscall+0x345
> Xint0x80_syscall() at Xint0x80_syscall+0x20
> --- syscall (123, FreeBSD ELF32, fchown), eip = 0x280defa7, esp = 0xbfbfeb9c, ebp = 0xbfbfeca8 ---
> KDB: enter: panic
> [thread pid 984 tid 100087 ]
> Stopped at      kdb_enter+0x32: leave

Kernel with INVARIANTS, WITNESS and DEBUG_*LOCKS:

panic: System call write returning with 1 locks held
KDB: stack backtrace:
db_trace_self_wrapper(c0713383,cf35fc74,c053661a,c07106dd,c07877e0,...) at db_trace_self_wrapper+0x26
kdb_backtrace(c07106dd,c07877e0,c07321c9,cf35fc80,cf35fc80,...) at kdb_backtrace+0x29
panic(c07321c9,c070d9f4,1,c070d9f4,c0567fb8,...) at panic+0xaa
syscall(cf35fd38) at syscall+0x46c
Xint0x80_syscall() at Xint0x80_syscall+0x20
--- syscall (0, FreeBSD ELF32, nosys), eip = 0x281672a3, esp = 0xbfbfeb7c, ebp = 0xbfbfeb98 ---
KDB: enter: panic
[thread pid 1004 tid 100083 ]
Stopped at      kdb_enter+0x32: leave
db> show pcpu
cpuid        = 0
curthread    = 0xc2568210: pid 1004 "cpio"
curpcb       = 0xcf35fd90
fpcurthread  = none
idlethread   = 0xc1ffdc60: pid 10 "idle"
APIC ID      = 0
currentldt   = 0x50
spin locks held:
db> show locks
db> show alllocks
Process 945 (sshd) thread 0xc2392c60 (100070)
exclusive sx so_rcv_sx r = 0 (0xc2368cec) locked _at_ /vol/src/sys/kern/uipc_sockbuf.c:145
db> show lockedvnods
Locked vnodes

0xc2665570: tag fuse, type VREG
    usecount 1, writecount 1, refcount 1 mountedhere 0
    flags ()
    v_object 0xc2642aa8 ref 0 pages 0
     lock type fuse: EXCL (count 1) by thread 0xc2568210 (pid 1004)#0 0xc0525db6 at _lockmgr+0x596
#1 0xc05a5390 at vop_stdlock+0x40
#2 0xc06e5b35 at VOP_LOCK1_APV+0xa5
#3 0xc05bf3fd at _vn_lock+0xfd
#4 0xc23899cc at fuse_io_file+0x3c
#5 0xc05703f5 at dofilewrite+0x95
#6 0xc0570688 at kern_writev+0x58
#7 0xc05706ff at write+0x4f
#8 0xc06ce803 at syscall+0x2e3
#9 0xc06bccf0 at Xint0x80_syscall+0x20

nodeid: 11, parent_nid: 5, fh_counter: 1, nlookup: 1, flags: 0
db> 

Cheers,
Ulrich Spoerlein
-- 
It is better to remain silent and be thought a fool,
than to speak, and remove all doubt.