From 6857471cf3ec44101821a34c3d7dc18913d0c22b Mon Sep 17 00:00:00 2001 From: mdf Date: Wed, 28 Jul 2010 15:36:12 +0000 Subject: Add MALLOC_DEBUG_MAXZONES debug malloc(9) option to use multiple uma zones for each malloc bucket size. The purpose is to isolate different malloc types into hash classes, so that any buffer overruns or use-after-free will usually only affect memory from malloc types in that hash class. This is purely a debugging tool; by varying the hash function and tracking which hash class was corrupted, the intersection of the hash classes from each instance will point to a single malloc type that is being misused. At this point inspection or memguard(9) can be used to catch the offending code. Add MALLOC_DEBUG_MAXZONES=8 to -current GENERIC configuration files. The suggestion to have this on by default came from Kostik Belousov on -arch. This code is based on work by Ron Steinke at Isilon Systems. Reviewed by: -arch (mostly silence) Reviewed by: zml Approved by: zml (mentor) --- sys/ia64/conf/GENERIC | 1 + 1 file changed, 1 insertion(+) (limited to 'sys/ia64/conf') diff --git a/sys/ia64/conf/GENERIC b/sys/ia64/conf/GENERIC index cf06a29..71af42c 100644 --- a/sys/ia64/conf/GENERIC +++ b/sys/ia64/conf/GENERIC @@ -68,6 +68,7 @@ options UFS_GJOURNAL # Enable gjournal-based UFS journaling options WITNESS # Enable checks to detect deadlocks and cycles options WITNESS_SKIPSPIN # Don't run witness on spinlocks for speed options _KPOSIX_PRIORITY_SCHEDULING # Posix P1003_1B RT extensions +options MALLOC_DEBUG_MAXZONES=8 # Separate malloc(9) zones # Various "busses" device firewire # FireWire bus code -- cgit v1.1