From owner-freebsd-threads@FreeBSD.ORG  Thu Jan 31 09:36:13 2008
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
Delivered-To: freebsd-threads@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id D75C716A475;
	Thu, 31 Jan 2008 09:36:13 +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 A285813C4EF;
	Thu, 31 Jan 2008 09:36:13 +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 4E41647D36;
	Thu, 31 Jan 2008 04:36:13 -0500 (EST)
Date: Thu, 31 Jan 2008 09:36:13 +0000 (GMT)
From: Robert Watson <rwatson@FreeBSD.org>
X-X-Sender: robert@fledge.watson.org
To: Julian Elischer <julian@elischer.org>
In-Reply-To: <20080129222455.T53151@fledge.watson.org>
Message-ID: <20080131093321.K35034@fledge.watson.org>
References: <200801240850.m0O8o2JQ023500@freefall.freebsd.org>
	<4798564B.7070500@elischer.org>
	<Pine.GSO.4.64.0801240957550.16059@sea.ntplx.net>
	<20080128185830.B56811@fledge.watson.org>
	<479E3079.3000803@elischer.org>
	<20080129222455.T53151@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: Daniel Eischen <deischen@freebsd.org>,
	Gary Stanley <gary@velocity-servers.net>, freebsd-threads@freebsd.org
Subject: Re: threads/119920: fork broken in libpthread
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>, 
	<mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Jan 2008 09:36:13 -0000


On Tue, 29 Jan 2008, Robert Watson wrote:

>>> Should the patch be considered for an errata notice for 6.x?  Should we be 
>>> trying to MFC this to 7.x for inclusion with 7.0 or does it need more time 
>>> to shake out and should potentially be a 7.0 errata notice or just appear 
>>> in 7.1?
>> 
>> yes and yes and no
>
> If the fix is going to ship in 7.0 and hasn't yet been MFC'd, that needs to 
> happen ASAP.  Could someone forward the patch/etc over to re@ for approval?
>
> The procedure for doing an errata patch is basically that whoever is 
> proposing the errata patch needs to e-mail a patch, or multiple patches if 
> it's different for different branches, a proposed branch list, and as much 
> of a completed errata notice template as possible (impact, etc) to re@ for 
> review. Once re@ is OK that it's ready to go, it will get sent over to 
> secteam@ to be put into production, binary updates generated, etc.  If in 
> doubt about which branches, drop e-mail to secteam@ to ask which are 
> supported, etc.
>
> At this point we would probably not advise doing the errata patch before 7.0 
> is released, so priority should go to preparing any patches that need to go 
> out with 7.0.

Hello?

Right now this is on re@'s list of "waiting for this to do RC2", which means 
that the release is holding on the fix.  Please let me know what the plan is 
so we can either move on with the release without waiting, or have some sort 
of timeline in mind.  Is this patch believed mature enough to be merged as-is?

Thanks,

Robert N M Watson
Computer Laboratory
University of Cambridge