From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@labs.coraid.com>
Date: Tue, 26 Oct 2010 10:31:32 -0400
To: lucio@proxima.alt.za, 9fans@9fans.net
Message-ID: <7e60107b49c4d164c977e1de7a701967@coraid.com>
In-Reply-To: <20101026134509.GD3068@fangle.proxima.alt.za>
References: <e6955ff428124877861dddfe0be6fd6e@gmx.de>
	<3722191d11202554e3bed26da57f5062@plug.quanstro.net>
	<20101026134509.GD3068@fangle.proxima.alt.za>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] lock diagnostics on Fossil server
Topicbox-Message-UUID: 6d675588-ead6-11e9-9d60-3106f5b1d025

> I was hoping you'd follow up on that, I needed a seed message and my
> mailbox has recently overflowed :-(
>
> I'm curious what you call "crash" in this case and I think Cinap is too.
> Basically, exactly what happens in the situation when a nil pointer is
> dereferenced in the kernel?  How does the kernel survive and slip into
> a locked situation?

good point.  usually you get a panic message, registers and a stack
dump.  i may be recalling the problem incorrectly.

> I really appreciate the fix, it certainly had the desired effect.

well, that's good.

- erik