Re: kern/40163: mv(1) cause WAPBL panic

["Jared D. McNeill" <jmcneill%invisible.ca@localhost>]

The following reply was made to PR kern/40163; it has been noted by GNATS.

From: "Jared D. McNeill" <jmcneill%invisible.ca@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, 
netbsd-bugs%netbsd.org@localhost
Subject: Re: kern/40163: mv(1) cause WAPBL panic
Date: Fri, 12 Dec 2008 21:20:02 -0500 (EST)

 On Sat, 13 Dec 2008, lloyd%must-have-coffee.gen.nz@localhost wrote:
 >> Description:
 > Typing "mv foo/foo ." causes a panic if the filesystem in question has 
 > logging enabled.
 
 I am able to reproduce this on 5.0 also, note that foo/foo must be a 
 directory and not a regular file. Here's the panic, hand-copied:
 
 Reader/writer lock error: rw_vector_enter: locking against myself
 
 lock address : 0x00000000ce211c30
 current cpu  :                  0
 current lwp  : 0x00000000cc5b65e0
 owner/count  : 0x00000000cc5b65e0 flags      : 0x0000000000000004
 
 panic: lock error
 fatal breakpoint trap in supervisor mode
 trap type 1 code 0 eip c053bc4c cs 8 eflags 246 cr2 bbb8cbe0 ilevel 0
 Stopped in pid 515.1 (mv) at    netbsd:breakpoint+0x4:  popl    %ebp
 db{0}> tr
 breakpoint(..)
 panic(..)
 lockdebug_abort(..)
 rw_abort(..)
 rw_vector_enter(..)
 vlockmgr(..)
 ffs_lock(..)
 VOP_LOCK(..)
 vn_lock(..)
 wapbl_ufs_rename(..)
 ufs_rename(..)
 VOP_RENAME(..)
 do_sys_rename(..)
 sys_rename(..)
 syscall(..)