Date: Wed, 5 Nov 2008 11:41:27 -0500 From: John Baldwin <jhb@freebsd.org> To: freebsd-current@freebsd.org Cc: current@freebsd.org Subject: Re: panic: tmpfs_alloc_vp: type 0xffffff000143d380 0 Message-ID: <200811051141.27965.jhb@freebsd.org> In-Reply-To: <d227e09e0811050434p3f847a77i3c6eb120883baf3c@mail.gmail.com> References: <d227e09e0811050434p3f847a77i3c6eb120883baf3c@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 05 November 2008 07:34:56 am Pawel Worach wrote: > Hi, > > Got the following panic after I built some ports with > WRKDIRPREFIX=/tmp/work where /tmp is tmpfs. > > FreeBSD one 8.0-CURRENT FreeBSD 8.0-CURRENT #0 r184639M: Tue Nov 4 > 18:39:44 CET 2008 root@one:/usr/obj/usr/src/sys/IBMT61 amd64 > > panic: tmpfs_alloc_vp: type 0xffffff000143d380 0 > > Unread portion of the kernel message buffer: > panic: tmpfs_alloc_vp: type 0xffffff000143d380 0 > cpuid = 0 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > panic() at panic+0x17d > tmpfs_alloc_vp() at tmpfs_alloc_vp+0x255 > tmpfs_lookup() at tmpfs_lookup+0x17a > vfs_cache_lookup() at vfs_cache_lookup+0xda I'm guessing the parent node of a file got free'd (maybe a missing refcount?) and that tn_parent is a stale pointer. Not sure how that would have happened though. Might be worth looking at the node passed to tmpfs_alloc_vp(). -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200811051141.27965.jhb>