From owner-freebsd-current@FreeBSD.ORG Fri Aug 8 06:56:50 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 16CC137B401 for ; Fri, 8 Aug 2003 06:56:50 -0700 (PDT) Received: from godel.mtl.distributel.net (nat.MTL.distributel.NET [66.38.181.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5AB6143FA3 for ; Fri, 8 Aug 2003 06:56:49 -0700 (PDT) (envelope-from bmilekic@technokratis.com) Received: from godel.mtl.distributel.net (localhost [127.0.0.1]) h789ujPM005977; Fri, 8 Aug 2003 09:56:45 GMT (envelope-from bmilekic@technokratis.com) Received: (from bmilekic@localhost) by godel.mtl.distributel.net (8.12.9/8.12.9/Submit) id h789ujfM005976; Fri, 8 Aug 2003 09:56:45 GMT X-Authentication-Warning: godel.mtl.distributel.net: bmilekic set sender to bmilekic@technokratis.com using -f Date: Fri, 8 Aug 2003 09:56:45 +0000 From: Bosko Milekic To: Mike Silbersack Message-ID: <20030808095645.GA5897@technokratis.com> References: <20030807173447.H39389@odysseus.silby.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030807173447.H39389@odysseus.silby.com> User-Agent: Mutt/1.4.1i cc: current@freebsd.org Subject: Re: another buildworld -j4 panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Aug 2003 13:56:50 -0000 On Thu, Aug 07, 2003 at 05:36:38PM -0500, Mike Silbersack wrote: > > ok, here goes: > > duplicate free from zone FFS1 dinode > > traceback: > Debugger > panic > uma_dbg_free > uma_zfree_arg > ffs_ifree > ufs_reclaim > ufs_vnoperate > vclean > gdonel > getnewvnode > ffs_vget > ufs_lookup > ufs_vnoperate > vfs_cache_lookup > ufs_vnoperate > lookup > namei > stat > syscall > Xint0x80_syscall > > Whee! geez, you're really hitting a lot of double frees. Can the other people running -current under high load turn on INVARIANTS and see if they start hitting the double free problems, too? I'd like some more evidence. Judging from the things we've seen from your traces I would guess at this point that there is a path somewhere that ends up in the ffs code without Giant, and that code fails to assert Giant requirements most of the time. Maybe it's time we start sprinkling the GIANT_REQUIREDs where we know they belong... that one we talked about adding the other day, did it catch anything? -- Bosko Milekic * bmilekic@technokratis.com * bmilekic@FreeBSD.org TECHNOkRATIS Consulting Services * http://www.technokratis.com/