From owner-freebsd-current@FreeBSD.ORG  Wed Jun  2 12:52:05 2004
Return-Path: <owner-freebsd-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 0B90216A4CF; Wed,  2 Jun 2004 12:52:05 -0700 (PDT)
Received: from fledge.watson.org (fledge.watson.org [204.156.12.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id A045243D49; Wed,  2 Jun 2004 12:52:04 -0700 (PDT)
	(envelope-from robert@fledge.watson.org)
Received: from fledge.watson.org (localhost [127.0.0.1])
	by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i52JpLFT022294;
	Wed, 2 Jun 2004 15:51:21 -0400 (EDT)
	(envelope-from robert@fledge.watson.org)
Received: from localhost (robert@localhost)i52JpLcm022291;
	Wed, 2 Jun 2004 15:51:21 -0400 (EDT)
	(envelope-from robert@fledge.watson.org)
Date: Wed, 2 Jun 2004 15:51:21 -0400 (EDT)
From: Robert Watson <rwatson@FreeBSD.org>
X-Sender: robert@fledge.watson.org
To: Bosko Milekic <bmilekic@FreeBSD.org>
In-Reply-To: <20040602170800.GA56275@freefall.freebsd.org>
Message-ID: <Pine.NEB.3.96L.1040602154936.17221K-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: Divacky Roman <xdivac02@stud.fit.vutbr.cz>
cc: current@FreeBSD.org
Subject: Re: uipc_socket2.c panic
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
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: Wed, 02 Jun 2004 19:52:05 -0000

On Wed, 2 Jun 2004, Bosko Milekic wrote:

> You wrote:
> >Additional information (I forgot to mention it - I apology)
> >I am running with debug.mpsafenet=1
> 
>   This is highly relevant.  It means that there is probably a problem
>   in network locking somewhere.  I have CC'd Robert to make sure he
>   is in on the loop for this.

Actually, what it means is that someone didn't read the UPDATING entry
relating to debug.mpsafenet or the heads up message saying "Do not use
debug.mpsafenet=1".  Not all of the netperf work is merged yet, and
specifically, the socket locking isn't merged.  This could easily explain
socket buffer corruption.  I'll be merging a lot of that locking this
week, but until that merging is done, you don't want to run with
debug.mpsafenet=1 unless you're also running with the netperf patch set
at:

    http://www.watson.org/~robert/freebsd/netperf/

I'm in the throes of updating that patch for recent merges of accept
locking yesterday.

Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
robert@fledge.watson.org      Senior Research Scientist, McAfee Research