From owner-freebsd-current@FreeBSD.ORG Sun Jan 22 20:12:34 2006 Return-Path: X-Original-To: current@FreeBSD.org 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 9737516A41F for ; Sun, 22 Jan 2006 20:12:34 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5BB9643D46 for ; Sun, 22 Jan 2006 20:12:34 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 33FDC1A3C1C for ; Sun, 22 Jan 2006 12:12:34 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 5B43F512CE; Sun, 22 Jan 2006 15:12:33 -0500 (EST) Date: Sun, 22 Jan 2006 15:12:33 -0500 From: Kris Kennaway To: current@FreeBSD.org Message-ID: <20060122201233.GA59053@xor.obsecurity.org> References: <20060122194129.GZ69162@funkthat.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mP3DRpeJDSE+ciuQ" Content-Disposition: inline In-Reply-To: <20060122194129.GZ69162@funkthat.com> User-Agent: Mutt/1.4.2.1i Cc: Subject: Re: memory corruption in recent -current? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Sun, 22 Jan 2006 20:12:34 -0000 --mP3DRpeJDSE+ciuQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 22, 2006 at 11:41:29AM -0800, John-Mark Gurney wrote: > I've been working on a BT878 audio driver (first crack is available > in p4), and with a recent -current (you can sync to my -current as > it's the one in my workspace, jmg_carbon), I get memory corruption: > Memory modified after free 0xc2fb1050(12) val=3D1c @ 0xc2fb1050 > panic: Most recently used by ioctlops > or: > Memory modified after free 0xc2ba2b90(12) val=3D1c @ 0xc2ba2b90 > panic: Most recently used by Unitno >=20 > I went back to a kerenl that is pre-Dec 21st, and I haven't had a single > panic yet. I will admit I haven't done a builtworld between the these > two (the last buildworld matched with the pre-Dec 21st kernel)... I am > using kld modules for my testing, so I was building modules against an > old world, but I don't know of anything that has changed that would > cause problems.. >=20 > Anyone else seeing this? Use memguard to track down the cause. Kris --mP3DRpeJDSE+ciuQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFD0+cwWry0BWjoQKURArF1AKDw0PDjCugWDWu+g/NdB0QratpWGgCdHi/L r/WiJfqnoCNlpgvHOAcv34o= =NVRM -----END PGP SIGNATURE----- --mP3DRpeJDSE+ciuQ--