Date: Sun, 26 Jun 2005 04:23:46 -0500 (CDT) From: Mike Silbersack <silby@silby.com> To: Thierry Herbelot <thierry@herbelot.com> Cc: freebsd-current@freebsd.org, current@freebsd.org Subject: Re: Mbuf double-free guilty party detection patch Message-ID: <20050626042202.W7093@odysseus.silby.com> In-Reply-To: <200506261049.42303.thierry@herbelot.com> References: <20050624212729.C537@odysseus.silby.com> <20050626012002.H935@odysseus.silby.com> <20050626064309.GA4700@nagual.pp.ru> <200506261049.42303.thierry@herbelot.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 26 Jun 2005, Thierry Herbelot wrote: > still no good luck : after using the second patch, no panic, but the debug > messages seem incomplete : (last freed by: /0/) > > This memory last freed by: 0 > Memory modified after free 0xc15d5800(256) val=800 @ 0xc15d583c > This memory last freed by: 0 > Memory modified after free 0xc15d5800(256) val=0 @ 0xc15d5840 > This memory last freed by: 0 > Memory modified after free 0xc15d5800(256) val=3 @ 0xc15d5844 Well, since I store the address inside of the mbuf, if whatever reuses it zeros it out, we'll see zero. :( Once I have memguard modified, we'll see what we can learn. > the test case is : building the kernel while tar-ing the src tree over two > separate ssh session. > > TfH > > PS : what is puzzling is that I've got another machine running a more recent > -current, with no ill effects (but it uses an ed(4) I/F) It'll be interesting to learn the answer. :) Mike "Silby" Silbersack
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050626042202.W7093>