From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 17 09:37:23 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B0E916A4CE for ; Sat, 17 Jan 2004 09:37:23 -0800 (PST) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id B897D43D49 for ; Sat, 17 Jan 2004 09:37:21 -0800 (PST) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.10/8.12.9) with ESMTP id i0HHbHET036526; Sat, 17 Jan 2004 10:37:17 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sat, 17 Jan 2004 10:37:17 -0700 (MST) Message-Id: <20040117.103717.07694079.imp@bsdimp.com> To: twohey@CS.Stanford.EDU From: "M. Warner Losh" In-Reply-To: References: X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org Subject: Re: [CHECKER] bugs in FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Jan 2004 17:37:23 -0000 In message: Paul Twohey writes: : Hi, : : I'm with the Stanford Metacompilation research group. We have a suite of : checkers that find bugs at compile time and we've had quite a bit of : success checking the Linux kernel code for errors. Since our checkers can : emit false alarms we filter the reports before we give them to the kernel : developers. While some false alarms slip past us to the developers, our : limited knowledge of the kernel allows us to recognize most of them. : : We are currently trying to extend our checker to automatically find : functions which allocate resources and to make sure those resources are : properly disposed of. : : Enclosed is a list of potential bugs in FreeBSD where a value is returned : from a function (like malloc) that should be owned by the caller and the : caller does not properly dispose of the value with the appropriate : disposal routine (like free). : : Confirmation of these reports would be appreciated. Wow! That's cool! You've found a number of problems. It will take us a little while to chew through them (although on their face they do seem to be issues). Warner