From owner-freebsd-current@FreeBSD.ORG  Mon Aug 15 00:33:58 2011
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 03798106566C
	for <current@FreeBSD.org>; Mon, 15 Aug 2011 00:33:58 +0000 (UTC)
	(envelope-from rwatson@FreeBSD.org)
Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42])
	by mx1.freebsd.org (Postfix) with ESMTP id D2D4D8FC14
	for <current@FreeBSD.org>; Mon, 15 Aug 2011 00:33:57 +0000 (UTC)
Received: from fledge.watson.org (fledge.watson.org [65.122.17.41])
	by cyrus.watson.org (Postfix) with ESMTPS id 6EF6146B39
	for <current@FreeBSD.org>; Sun, 14 Aug 2011 20:33:57 -0400 (EDT)
Date: Mon, 15 Aug 2011 01:33:57 +0100 (BST)
From: Robert Watson <rwatson@FreeBSD.org>
X-X-Sender: robert@fledge.watson.org
To: current@FreeBSD.org
Message-ID: <alpine.BSF.2.00.1108150130240.63057@fledge.watson.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Cc: 
Subject: Avoid kernels between r224778 and r224841; bug causes buildworld
 failure
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Aug 2011 00:33:58 -0000


Dear all:

As you may have seen from current@ traffic, a bug crept in during the Capsicum 
merge, introduced by the infamous Last Minute Cleanup and not caught in 
pre-commit testing.  The most noticed effect of the bug is to cause buildworld 
to fail due to a problem with /dev/{stdin,stdout,stderr} when running an 
affected kernel.  The bug doesn't break buildkernel, so it's possible to 
update from bad revisions by doing that (or rolling back to a pre-update 
kernel).  The problem appeared in r224778 (11 August), and was fixed in 
r224842 (13 August), so it's a pretty short window and hopefully the problem 
will scroll out quickly.

I'm currently awaiting approvel from re@ to commit a note to UPDATING saying 
the above.

Sorry about that!

Robert N M Watson
Computer Laboratory
University of Cambridge