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

[Greg Oster <oster%cs.usask.ca@localhost>]

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

From: Greg Oster <oster%cs.usask.ca@localhost>
To: lloyd%must-have-coffee.gen.nz@localhost
Cc: gnats-bugs%NetBSD.org@localhost
Subject: Re: kern/40163: mv(1) cause WAPBL panic 
Date: Fri, 12 Dec 2008 20:12:56 -0600

 lloyd%must-have-coffee.gen.nz@localhost writes:
 > >Number:         40163
 > >Category:       kern
 > >Synopsis:       mv(1) cause WAPBL panic
 > >Confidential:   no
 > >Severity:       critical
 > >Priority:       high
 > >Responsible:    kern-bug-people
 > >State:          open
 > >Class:          sw-bug
 > >Submitter-Id:   net
 > >Arrival-Date:   Sat Dec 13 02:00:00 +0000 2008
 > >Originator:     Lloyd Parkes
 > >Release:        5.0_BETA
 > >Organization:
 > Must Have Coffee
 > >Environment:
 > NetBSD maro.must-have-coffee.gen.nz 5.0_BETA NetBSD 5.0_BETA (GENERIC) #0: Tu
 > e Dec  2 21:58:06 NZDT 2008  
 > lloyd%maro.must-have-coffee.gen.nz@localhost:/vol/scratch/
 > obj/amd64/sys/arch/amd64/compile/GENERIC amd64
 > >Description:
 > Typing "mv foo/foo ." causes a panic if the filesystem in question has loggin
 > g enabled.
 > 
 > 
 > >How-To-Repeat:
 > Type "mv foo/foo ."
 > >Fix:
 > None.
 
 Could you please provide the full trace of the panic?  It doesn't 
 appear like this problem is repeatable on any of the systems I have 
 access to.... 
 
 Thanks.
 
 Later...
 
 Greg Oster