Re: kern/46221: Kernel panic in NFS server code

[Matthias Scheler <tron%zhadum.org.uk@localhost>]

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

From: Matthias Scheler <tron%zhadum.org.uk@localhost>
To: Manuel Bouyer <bouyer%antioche.eu.org@localhost>
Cc: gnats-bugs%NetBSD.org@localhost
Subject: Re: kern/46221: Kernel panic in NFS server code
Date: Fri, 23 Mar 2012 14:11:06 +0000

 On Fri, Mar 23, 2012 at 10:33:49AM +0100, Manuel Bouyer wrote:
 > > The new code in ufs_fhtovp() finally triggered.
 > > Here is the output of vprint():
 > > 
 > > ufs_fhtovp: ip == NULL on vp %p
 > > : vnode @ 0xfffffe8169463be0, flags (0x80010<MPSAFE,CLEAN>)
 > >         tag VT_NON(0), type VREG(1), usecount 1, writecount 0, holdcount 0
 > >         freelisthd 0x0, mount 0xfffffe8214f82000, data 0x0 lock 
 > > 0xfffffe8169463cf0
 > 
 > So it got a clean vnode. This is bad.
 > I suspect ufs_ihashget() is returnning the clean vnode; otherwise it has to 
 > be
 > in ffs_vget() itself.
 > 
 > Can you run a kernel with the attached patch and see if one of the KASSERT
 > fires ? You can probably turn the check to a printf if you want to
 > avoid the panic.
 
 I'm currently testing a kernel Juergen Hannken-Illjes's patch
 if that is alright.
 
        Kind regards
 
 -- 
 Matthias Scheler                                  http://zhadum.org.uk/