cvs commit: src/sys/kern kern_malloc.c src/share/man/man9 Makefile redzone.9 src/sys/vm redzone.c redzone.h src/sys/conf NOTES files options

Andrew Gallatin gallatin at
Wed Feb 1 08:44:37 PST 2006

Steve Kargl writes:
 > On Wed, Feb 01, 2006 at 10:47:52AM -0500, Andrew Gallatin wrote:
 > > WARNING: WITNESS option enabled, expect reduced performance.
 > > Memory modified after free 0xffffff0000006d00(248) val=5 @ 0xffffff0000006dd0
 > > kernel trap 9 with interrupts disabled
 > You can trigger this panic without the red zone stuff.
 > See my string of post from yesterday.  Something went

Your panic looks like the same panic as mine, but with memguard rather
than redzone.  These systems do similar things, I suppose it is only
natural that they'd be hit by the same bug.

 > into sys/ on 2006-01-26 that is causing the problems.
 > I suspect the pts code, but can't prove it, yet.

I built a kernel without 'device pty' thus removing the pts code, and
I still see the same panic with redzone enabled.  Perhaps your initial
panic is the result of the pts code, but this memguard/redzone panic
is different, and may not be related.

My original question still stands: Does redzone work in combination
with INVARIANTS on other platforms?  Amd64 is the only -current
platform I'm running...


More information about the cvs-src mailing list