From 656331798ebcd8c5d717f6f5581b0aea54c45072 Mon Sep 17 00:00:00 2001
From: deraadt <>
Date: Wed, 5 Dec 2001 09:49:39 +0000
Subject: [PATCH] document how malloc(0) blobbies are stored, and their
 character

---
 src/lib/libc/stdlib/malloc.3 | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/src/lib/libc/stdlib/malloc.3 b/src/lib/libc/stdlib/malloc.3
index e5451bb7..8f05c38e 100644
--- a/src/lib/libc/stdlib/malloc.3
+++ b/src/lib/libc/stdlib/malloc.3
@@ -34,7 +34,7 @@
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
-.\"	$OpenBSD: malloc.3,v 1.23 2001/11/05 21:31:21 millert Exp $
+.\"	$OpenBSD: malloc.3,v 1.24 2001/12/05 09:49:39 deraadt Exp $
 .\"
 .Dd August 27, 1996
 .Dt MALLOC 3
@@ -81,6 +81,11 @@ or larger, the memory returned will be page-aligned.
 Allocation of a zero size object returns a pointer to a zero size object.
 This zero size object is access protected, so any access to it will
 generate an exception (SIGSEGV).
+Many zero-sized objects can be placed consecutively in shared
+protected pages.
+The minimum size of the protection on each object is suitably aligned and
+sized as previously stated, but the protection may extend further depending
+on where in a protected zone the object lands.
 .Pp
 The
 .Fn calloc