Re: kern/40525: panic: ffs_valloc: dup alloc

[David Holland <dholland-bugs%netbsd.org@localhost>]

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

From: David Holland <dholland-bugs%netbsd.org@localhost>
To: Juergen Hannken-Illjes <hannken%eis.cs.tu-bs.de@localhost>
Cc: kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
        gnats-bugs%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost, 
dholland%netbsd.org@localhost
Subject: Re: kern/40525: panic: ffs_valloc: dup alloc
Date: Sat, 7 Feb 2009 21:21:15 +0000

 On Sat, Jan 31, 2009 at 11:40:04AM +0000, Juergen Hannken-Illjes wrote:
  > From: Juergen Hannken-Illjes <hannken%eis.cs.tu-bs.de@localhost>
  > To: gnats-bugs%netbsd.org@localhost
  > Cc: 
  > Subject: Re: kern/40525: panic: ffs_valloc: dup alloc
  > Date: Sat, 31 Jan 2009 12:38:18 +0100
  > 
  >  On Sat, Jan 31, 2009 at 08:30:00AM +0000, dholland%netbsd.org@localhost 
wrote:
  >  > ffs (non-wapbl, non-softdep) panic allocating an already allocated inode.
  >  > See thread on current-users starting here:
  >  > 
  >  >    http://mail-index.netbsd.org/current-users/2009/01/10/msg007167.html
  >  > 
  >  > I'd like a second opinion before I commit it, in case I've overlooked
  >  > something.
  >  
  >  Looks good to me -- as long as it only happens on UFS2 file systems.
 
 I don't see what's UFS2-specific about it?
 
 But it sounds like you agree that my patch fixes *a* bug, even if it's
 not the same bug reported on current-users. Right?
 
 -- 
 David A. Holland
 dholland%netbsd.org@localhost