Date: Tue, 28 Sep 2004 12:09:54 -0400 From: Ken Smith <kensmith@cse.Buffalo.EDU> To: John Baldwin <jhb@freebsd.org> Cc: sparc64@freebsd.org Subject: Re: Memory modified after free 0xfffff8001b210e00(504) val=deadc0dd @ 0xfffff8001b21 Message-ID: <20040928160953.GC27640@electra.cse.Buffalo.EDU> In-Reply-To: <200409281131.03448.jhb@FreeBSD.org> References: <20040921064450.GA54998@xor.obsecurity.org> <20040928071241.GA74512@xor.obsecurity.org> <200409281131.03448.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Sep 28, 2004 at 11:31:03AM -0400, John Baldwin wrote:
> On Tuesday 28 September 2004 03:12 am, Kris Kennaway wrote:
> > > I just got this panic on an SMP sparc package machine running 6.0:
> > >
> > > Memory modified after free 0xfffff8001b210e00(504) val=deadc0dd @
> > > 0xfffff8001b210f20 panic: Most recently used by file desc
>
> Unfortunately it's hard to track these down as we really need to know where it
> was free'd() from and UMA/malloc do not currently have the ability to tell us
> that.
What scares me is he keeps sending them here to the sparc64 list and I
haven't seen him send any to other lists... [ Just kidding Kris! :-]
But ... Where might a file desc structure be mis-handled that would
be specific to sparc64? That's what is a little scary...
--
Ken Smith
- From there to here, from here to | kensmith@cse.buffalo.edu
there, funny things are everywhere. |
- Theodore Geisel |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040928160953.GC27640>