From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <7263abf35d27585b2194aec537832bdc@quanstro.net>
From: erik quanstrom <quanstro@quanstro.net>
Date: Wed, 21 Nov 2007 08:22:48 -0500
To: 9fans@cse.psu.edu
Subject: Re: [9fans] kernel memory allocator got confused?
In-Reply-To: <d81908eb510fb7c7281f68d2486a7e9b@quintile.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 065842d8-ead3-11e9-9d60-3106f5b1d025

the problem appears to be detected here:

/sys/src/libc/port/pool.c:833: 					printblock(p, b, "mem user overflow");

so either your memory has gone wonky or the kernel is writing past the
end of the buffer.  

this must be in the kernel where the overflow is occuring.
it appears the reason you don't panic on the spot is because of this:

/sys/src/9/port/alloc.c:28: 	.flags=	POOL_TOLERANCE,

if you're feeling brave, you could recompile without POOL_TOLERANCE
and try to recreate the problem.  it'd be nice to know who's screwing up.
but .. that's not too much fun when you have an all-in-wonder
box.  maybe make a copy of fossil's stuff before trying.

- erik