From owner-freebsd-stable@FreeBSD.ORG Sun Apr 20 17:17:18 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 357F61065671; Sun, 20 Apr 2008 17:17:18 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 0942C8FC21; Sun, 20 Apr 2008 17:17:17 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 6FF0B46B61; Sun, 20 Apr 2008 13:17:17 -0400 (EDT) Date: Sun, 20 Apr 2008 18:17:17 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: "Bruce M. Simpson" In-Reply-To: <48087FD7.5070900@FreeBSD.org> Message-ID: <20080420181515.E92282@fledge.watson.org> References: <01ab01c898ca$ce4763e0$6ad62ba0$@muni.cz> <200804080957.30738.jhb@freebsd.org> <47FBB24B.60504@FreeBSD.org> <48087FD7.5070900@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Petr Holub , re@FreeBSD.org, freebsd-stable@freebsd.org, John Baldwin Subject: Re: panics on 6.3-RELEASE in IP stack X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Apr 2008 17:17:18 -0000 On Fri, 18 Apr 2008, Bruce M. Simpson wrote: >> I concur, this fix should really be MFCed. The problem went away in 7.x due >> to a total rewrite. I am distracted by other stuff at the moment, so, >> starter's orders... > > This just bit me. The fix is in RELENG_6, but it is not present after the > -p1 tag. So updating to STABLE should fix the problem for Petr. > > Whilst 6 is no longer the STABLE branch, I think this really should go onto > 6 in case any other releases happen from that branch. There are (tentative) plans to release a 6.4-RELEASE, but I don't think there's a schedule yet. Developers should plan on continuing to merge changes, especially bug fixes, to RELENG_6. Robert N M Watson Computer Laboratory University of Cambridge