Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 24 Jan 2006 09:03:55 -0500
From:      Kris Kennaway <kris@obsecurity.org>
To:        Kris Kennaway <kris@obsecurity.org>, current@FreeBSD.org
Subject:   Re: memory corruption in recent -current?
Message-ID:  <20060124140354.GB66330@xor.obsecurity.org>
In-Reply-To: <20060124082755.GB69162@funkthat.com>
References:  <20060122194129.GZ69162@funkthat.com> <20060122201233.GA59053@xor.obsecurity.org> <20060124082755.GB69162@funkthat.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--uQr8t48UFsdbeI+V
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jan 24, 2006 at 12:27:55AM -0800, John-Mark Gurney wrote:
> Kris Kennaway wrote this message on Sun, Jan 22, 2006 at 15:12 -0500:
> > 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 sin=
gle
> > > 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?
> >=20
> > Use memguard to track down the cause.
>=20
> Well, looks like memguard is broken?  I just ran it, and got this
> panic:

I run it on a number of my 'production' machines, so I don't think it
can be this broken everywhere.  Perhaps it's interacting badly with
your code :(

Kris

--uQr8t48UFsdbeI+V
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)

iD8DBQFD1jPKWry0BWjoQKURAtiJAJ0ergNBFBvhfmvc+Q4WqamSkGT6cQCgiFMp
yAX6v5iT3khZ9eq3wislSD8=
=Tgi3
-----END PGP SIGNATURE-----

--uQr8t48UFsdbeI+V--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060124140354.GB66330>