From owner-freebsd-current@FreeBSD.ORG  Thu May  7 12:59:49 2009
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 1DDC5106564A
	for <freebsd-current@freebsd.org>; Thu,  7 May 2009 12:59:49 +0000 (UTC)
	(envelope-from ben@wanderview.com)
Received: from mail.wanderview.com (mail.wanderview.com [66.92.166.102])
	by mx1.freebsd.org (Postfix) with ESMTP id A3CAF8FC18
	for <freebsd-current@freebsd.org>; Thu,  7 May 2009 12:59:48 +0000 (UTC)
	(envelope-from ben@wanderview.com)
Received: from harkness.in.wanderview.com (harkness.in.wanderview.com
	[10.76.10.150]) (authenticated bits=0)
	by mail.wanderview.com (8.14.3/8.14.3) with ESMTP id n47CxkZ6008888
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Thu, 7 May 2009 12:59:46 GMT (envelope-from ben@wanderview.com)
Message-Id: <619B386D-9FF5-4296-BB83-245881CA9C41@wanderview.com>
From: Ben Kelly <ben@wanderview.com>
To: Richard Todd <rmtodd@ichotolot.servalan.com>
In-Reply-To: <20090506234631.231A5CD8@mx1.synetsystems.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Thu, 7 May 2009 08:59:45 -0400
References: <20090506234631.231A5CD8@mx1.synetsystems.com>
X-Mailer: Apple Mail (2.930.3)
X-Spam-Score: -1.44 () ALL_TRUSTED
X-Scanned-By: MIMEDefang 2.64 on 10.76.20.1
Cc: freebsd-current@freebsd.org
Subject: Re: Panic: wrong vnode type 0xffffff009b7719c0 on yesterday's
	current.
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 07 May 2009 12:59:49 -0000

On May 6, 2009, at 6:54 PM, Richard Todd wrote:
> Hi. I updated my main -current box to the current sources as of  
> yesterday,
> and I've managed to twice get the "wrong vnode panic" out of the  
> cache_enter
> code.  As you can see from the backtrace down at cache_enter at  
> frame 11,
> the code is apparently expecting vp to point to a VDIR vnode, but  
> instead
> it's pointing to a VLNK.   (I've got another, similar, dump where vp  
> is
> pointing to a VREG node.)  In both cases, I was running tinderbox to  
> build
> packages, with resulting heavy use of both zfs (the underlying  
> filesystem)
> and nullfs, if that's relevant.

> (kgdb) l
> 697                     if (dvp->v_cache_dd != NULL) {
> 698                         CACHE_WUNLOCK();
> 699                         cache_free(ncp);
> 700                         return;
> 701                     }
> 702                     KASSERT(vp == NULL || vp->v_type == VDIR,
> 703                         ("wrong vnode type %p", vp));
> 704                     dvp->v_cache_dd = ncp;
> 705             }
> 706

It looks like this KASSERT was added relatively recently as part of  
the dotdot changes to the namecache:

   http://svn.freebsd.org/viewvc/base?view=revision&revision=190945

Perhaps there is further fallout from the changes that only occur with  
ZFS?

- Ben