Date: Thu, 26 Jan 2006 00:20:08 -0800 From: John-Mark Gurney <gurney_j@resnet.uoregon.edu> To: current@FreeBSD.org Subject: Re: memory corruption in recent -current? Message-ID: <20060126082007.GM69162@funkthat.com> In-Reply-To: <20060122194129.GZ69162@funkthat.com> References: <20060122194129.GZ69162@funkthat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
John-Mark Gurney wrote this message on Sun, Jan 22, 2006 at 11:41 -0800:
> 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=1c @ 0xc2fb1050
> panic: Most recently used by ioctlops
> or:
> Memory modified after free 0xc2ba2b90(12) val=1c @ 0xc2ba2b90
> panic: Most recently used by Unitno
>
> 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..
Well, turns out to be a bug in my driver.. the allocation scheme must
of changed causing it more likely to hit the buffer I had overwritten..
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060126082007.GM69162>