From owner-freebsd-stable@FreeBSD.ORG  Tue May 10 13:21:19 2005
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 859D416A4D1; Tue, 10 May 2005 13:21:19 +0000 (GMT)
Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id CFF8F43D31; Tue, 10 May 2005 13:21:18 +0000 (GMT)
	(envelope-from rwatson@FreeBSD.org)
Received: from fledge.watson.org (fledge.watson.org [204.156.12.50])
	by cyrus.watson.org (Postfix) with ESMTP id 408E546B28;
	Tue, 10 May 2005 09:21:14 -0400 (EDT)
Date: Tue, 10 May 2005 14:25:32 +0100 (BST)
From: Robert Watson <rwatson@FreeBSD.org>
X-X-Sender: robert@fledge.watson.org
To: Marc Olzheim <marcolz@stack.nl>
In-Reply-To: <20050510131005.GA4083@stack.nl>
Message-ID: <20050510142448.G9972@fledge.watson.org>
References: <20050503150014.GG17096@stack.nl> <20050510131005.GA4083@stack.nl>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
cc: freebsd-stable@freebsd.org
cc: bug-followup@FreeBSD.org
Subject: Re: kern/78824: race condition close()ing and read()ing the same
 socketpair on SMP.
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 10 May 2005 13:21:19 -0000


On Tue, 10 May 2005, Marc Olzheim wrote:

> On Tue, May 03, 2005 at 05:00:14PM +0200, Marc Olzheim wrote:
>> Is this going to be fixed before 5.4 ? It still breaks on today's
>> 5.4-STABLE.
>
> As this is the only issue known to me now, that I don't have a patch for 
> and is standing in my way of upgrading from FreeBSD 4.x to 5.x, I would 
> like to know whether this is a simple bug that could be fixed in a 
> second or not... If there are any issues (like being able to reproduce 
> it) or not, please let me know where I can be of assistance.

Marc,

I'll try to take a look at it on the plane today.  I've mostly been on 
travel the last month, so haven't had a chance to investigate in detail as 
yet.  Sorry about that, and thanks for the report!

Robert N M Watson