From owner-cvs-all  Tue Sep 29 23:14:06 1998
Return-Path: <owner-cvs-all>
Received: (from daemon@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id XAA00770
          for cvs-all-outgoing; Tue, 29 Sep 1998 23:14:06 -0700 (PDT)
          (envelope-from owner-cvs-all)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA00765;
          Tue, 29 Sep 1998 23:14:04 -0700 (PDT)
          (envelope-from jb@FreeBSD.org)
From: John Birrell <jb@FreeBSD.ORG>
Received: (from jb@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id XAA10772;
	Tue, 29 Sep 1998 23:14:00 -0700 (PDT)
Date: Tue, 29 Sep 1998 23:14:00 -0700 (PDT)
Message-Id: <199809300614.XAA10772@freefall.freebsd.org>
To: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG
Subject: cvs commit: src/lib/libc/stdlib malloc.c
Sender: owner-cvs-all@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

jb          1998/09/29 23:13:59 PDT

  Modified files:
    lib/libc/stdlib      malloc.c 
  Log:
  Delete the XXX comments that refer to spinlock recursion. The malloc/free/
  realloc functions check for recursion within the malloc code itself. In
  a thread-safe library, the single spinlock ensures that no two threads
  go inside the protected code at the same time. The thread implementation
  is responsible for ensuring that the spinlock does in fact protect malloc.
  There was a window of opportunity in which this was not the case. I'll fix
  that with a commit RSN.
  
  Revision  Changes    Path
  1.43      +1 -15     src/lib/libc/stdlib/malloc.c