From owner-freebsd-current@FreeBSD.ORG Wed Jun 29 08:26:11 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E9C4616A41C for ; Wed, 29 Jun 2005 08:26:11 +0000 (GMT) (envelope-from silby@silby.com) Received: from relay02.pair.com (relay02.pair.com [209.68.5.16]) by mx1.FreeBSD.org (Postfix) with SMTP id 692A243D5E for ; Wed, 29 Jun 2005 08:26:11 +0000 (GMT) (envelope-from silby@silby.com) Received: (qmail 94409 invoked from network); 29 Jun 2005 08:26:09 -0000 Received: from unknown (HELO localhost) (unknown) by unknown with SMTP; 29 Jun 2005 08:26:09 -0000 X-pair-Authenticated: 209.68.2.70 Date: Wed, 29 Jun 2005 03:25:53 -0500 (CDT) From: Mike Silbersack To: current@freebsd.org Message-ID: <20050629032309.E27720@odysseus.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Subject: mbuf trash-related "memory modified after free" panic fixed. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2005 08:26:12 -0000 Rev 1.9 of kern_mbuf.c contains a fix for the "memory modified after free" panics that have been cropping up recently. Bosko Milekic looked over what I had committed last week and found that I had forgotten one very important line of code. So, if you've been seeing such panics, please cvsup (or manually grab rev 1.9) and rebuild your kernel. If you're still seeing memory modified after free panics/prints after this upgrade, I definitely want to hear about it. Thanks, and sorry for panics. Mike "Silby" Silbersack