From owner-freebsd-current@FreeBSD.ORG Wed Feb 2 00:06:15 2005 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 0F44516A4CE for ; Wed, 2 Feb 2005 00:06:15 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id C04B743D2F for ; Wed, 2 Feb 2005 00:06:14 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id D770751471; Tue, 1 Feb 2005 16:06:13 -0800 (PST) Date: Tue, 1 Feb 2005 16:06:13 -0800 From: Kris Kennaway To: Peter Holm Message-ID: <20050202000613.GA9758@xor.obsecurity.org> References: <20050130094616.GA76093@peter.osted.lan> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="17pEHd4RhPHOinZp" Content-Disposition: inline In-Reply-To: <20050130094616.GA76093@peter.osted.lan> User-Agent: Mutt/1.4.2.1i cc: jroberson@chesapeake.net cc: current@freebsd.org Subject: Re: Panic: Memory modified after free 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: Wed, 02 Feb 2005 00:06:15 -0000 --17pEHd4RhPHOinZp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 30, 2005 at 10:46:16AM +0100, Peter Holm wrote: > With GENERIC HEAD from Jan 28 20:19 UTC + mpsafe_vfs =3D 1 I got: >=20 > Memory modified after free 0xc1d7c100(124) val=3Dc23fa000 @ 0xc1d7c164 >=20 > panic(c083d005,c083b16e,c083cfd6,c1d7c100,7c) at panic+0xef > mtrash_ctor(c1d7c100,80,0,402) at mtrash_ctor+0x4d > uma_zalloc_arg(c10526e0,0,402) at uma_zalloc_arg+0x14c > malloc(68,c08bcd60,402,c094f0c0,0) at malloc+0xae > inodedep_lookup(c167a000,193a1,1,cf261be0,c094f0c0) at inodedep_lookup+0x= a7 > softdep_change_linkcnt(c213b578,c6bc54f0,c65f3f88,c213b578,c1c39270) at s= oftdep_change_linkcnt+0x31 > ufs_dirremove(c17d83a8,c213b578,100800c,0,cf261c48) at ufs_dirremove+0x12d > ufs_remove(cf261c4c) at ufs_remove+0x4b > VOP_REMOVE_AP(cf261c4c) at VOP_REMOVE_AP+0x62 > kern_unlink(c1add2e0,bfbfe940,0,cf261d40,c07bd6c3) at kern_unlink+0x167 > unlink(c1add2e0,cf261d14,1,28,292) at unlink+0x12 > syscall(2804002f,bfbf002f,bfbf002f,2804f6c0,bfbfeb14) at syscall+0x213 >=20 > More info at http://www.holm.cc/stress/log/cons112.html > panic: Most recently used by inodedep You can try to use DEBUG_MEMGUARD with M_INODEDEP to find this. I'll add that to my SMP package machines to see if I can trigger it too. Kris --17pEHd4RhPHOinZp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCABl1Wry0BWjoQKURAo86AJwOi4YsNsThOjZL64aJBRcXtW1oJQCbBkXn caMc1rriaJ31QGoInhYyIqE= =hZUh -----END PGP SIGNATURE----- --17pEHd4RhPHOinZp--