[Bug 209158] node / npm triggering zfs rename deadlock

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209158

Doug Luce <doug at freebsd.con.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |doug at freebsd.con.com

--- Comment #1 from Doug Luce <doug at freebsd.con.com> ---
Same thing is happening for me:

% procstat -kk 2291
  PID    TID COMM             TDNAME           KSTACK
 2291 101307 node             -                mi_switch+0xe1
sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d kern_kevent+0x401
sys_kevent+0x12a amd64_syscall+0x351 Xfast_syscall+0xfb
 2291 101353 node             V8 WorkerThread  mi_switch+0xe1
sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125
do_sem_wait+0x4aa __umtx_op_sem_wait+0x73 amd64_syscall+0x351
Xfast_syscall+0xfb
 2291 101354 node             V8 WorkerThread  mi_switch+0xe1
sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125
do_sem_wait+0x4aa __umtx_op_sem_wait+0x73 amd64_syscall+0x351
Xfast_syscall+0xfb
 2291 101355 node             V8 WorkerThread  mi_switch+0xe1
sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125
do_sem_wait+0x4aa __umtx_op_sem_wait+0x73 amd64_syscall+0x351
Xfast_syscall+0xfb
 2291 101356 node             V8 WorkerThread  mi_switch+0xe1
sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125
do_sem_wait+0x4aa __umtx_op_sem_wait+0x73 amd64_syscall+0x351
Xfast_syscall+0xfb
 2291 101357 node             -                mi_switch+0xe1 sleepq_wait+0x3a
sleeplk+0x15d __lockmgr_args+0x902 vop_stdlock+0x3c VOP_LOCK1_APV+0xab
_vn_lock+0x43 zfs_lookup+0x3c2 zfs_freebsd_lookup+0x6d
VOP_CACHEDLOOKUP_APV+0xa1 vfs_cache_lookup+0xd6 VOP_LOOKUP_APV+0xa1
lookup+0x59c namei+0x4d4 kern_renameat+0x213 amd64_syscall+0x351
Xfast_syscall+0xfb
 2291 101358 node             -                mi_switch+0xe1 sleepq_wait+0x3a
sleeplk+0x15d __lockmgr_args+0x902 vop_stdlock+0x3c VOP_LOCK1_APV+0xab
_vn_lock+0x43 zfs_lookup+0x3c2 zfs_freebsd_lookup+0x6d
VOP_CACHEDLOOKUP_APV+0xa1 vfs_cache_lookup+0xd6 VOP_LOOKUP_APV+0xa1
lookup+0x59c namei+0x4d4 kern_renameat+0x213 amd64_syscall+0x351
Xfast_syscall+0xfb
 2291 101359 node             -                mi_switch+0xe1 sleepq_wait+0x3a
sleeplk+0x15d __lockmgr_args+0xc9e vop_stdlock+0x3c VOP_LOCK1_APV+0xab
_vn_lock+0x43 vputx+0x21f zfs_rename_unlock+0x3e zfs_freebsd_rename+0xcdf
VOP_RENAME_APV+0xab kern_renameat+0x3ef amd64_syscall+0x351 Xfast_syscall+0xfb
 2291 101360 node             -                mi_switch+0xe1 sleepq_wait+0x3a
sleeplk+0x15d __lockmgr_args+0x902 vop_stdlock+0x3c VOP_LOCK1_APV+0xab
_vn_lock+0x43 zfs_lookup+0x3c2 zfs_freebsd_lookup+0x6d
VOP_CACHEDLOOKUP_APV+0xa1 vfs_cache_lookup+0xd6 VOP_LOOKUP_APV+0xa1
lookup+0x59c namei+0x4d4 kern_renameat+0x213 amd64_syscall+0x351
Xfast_syscall+0xfb


Full thread dump at
https://gist.github.com/anonymous/3be664a893c8face928b678956b86302

-- 
You are receiving this mail because:
You are the assignee for the bug.