From owner-freebsd-arch Wed Apr 18 11:37:10 2001 Delivered-To: freebsd-arch@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id EE16137B43C for ; Wed, 18 Apr 2001 11:37:07 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA05138; Wed, 18 Apr 2001 11:37:05 -0700 Date: Wed, 18 Apr 2001 11:37:04 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Terry Lambert Cc: arch@freebsd.org Subject: Re: Reference counters In-Reply-To: <200104181826.LAA17706@usr02.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I tracked a similar bug in SunOS 3.5. It's nice to know things haven't changed. It actually turned out that the bug was a constantly incrementing crhold- not an extra crfree as people had been breaking their teeth on finding. Are there any spots in the code that do plain holds that do *not* imply the assignment of a credp into a structure? If you can assert that any crhold or crdup must return a pointer and any crfree must have an address of a pointer to NULL, you're probably most of the way toward finding the errant action. It also seems to me that one issue that can keep coming up is the freeing of the structure that has the credential- the freeing of that structure has to be still hand auditted to make sure crfree is done. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message