Date: Fri, 9 May 2003 10:43:13 -0400 From: Ali Bahar <alih@internetDog.org> To: freebsd-hackers@freebsd.org Subject: Re: cache_purge > cache_zap segmentation fault Message-ID: <20030509104313.B1465@internetDog.org> In-Reply-To: <20030509064025.GA91122@walton.maths.tcd.ie>; from dwmalone@maths.tcd.ie on Fri, May 09, 2003 at 07:40:25AM %2B0100 References: <20030508150341.B28906@internetDog.org> <1789.1052421172@critter.freebsd.dk> <20030508195410.A670@internetDog.org> <20030509064025.GA91122@walton.maths.tcd.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, May 09, 2003 at 07:40:25AM +0100, David Malone wrote:
> On Thu, May 08, 2003 at 07:54:10PM -0400, Ali Bahar wrote:
> > Considering its increasing frequency, I even suspected that the
> > filesystem had been corrupted -- in a way undetected by fsck. But, a
> To me it seems very unlikely that a corrupted filesystem would
> result in a corrupted name cache. The name cache is independendent
I understand, and agree.
> Mind you, I couldn't say for certain that some subtle corruption
> might not cause the problem.
_My_ perspective, too -- especially since I'm ignorant about the
filesystem code. :-)
> Is it possible that one of your modules is somehow stomping on
> memory that doesn't belong to it?
(Phrasing the right question is indeed half the solution.)
Excellent. Though this ought have been obvious to me, somehow I never
considered it plausible. Perhaps due to the presumed 'distance'
between the filesystem code, and my networking module! :-)
The possibility of memory overwrite by an in-development module is
about 3 orders of magnitude higher than the possibility of a name
cache bug. I can't yet see how it is happening, but I've seen weirder
coincidences in scribblers.
I'll look into this.
Thanks much for your help.
Much appreciated.
regards,
ali
--
Jesus was an Arab.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030509104313.B1465>