From owner-freebsd-threads@FreeBSD.ORG  Sun Aug 15 20:37:33 2004
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
Delivered-To: freebsd-threads@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id E444A16A4F5; Sun, 15 Aug 2004 20:37:33 +0000 (GMT)
Received: from fledge.watson.org (fledge.watson.org [204.156.12.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 8D9D043F54; Sun, 15 Aug 2004 20:13:52 +0000 (GMT)
	(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 i7FKC4XO064557;
	Sun, 15 Aug 2004 16:12:04 -0400 (EDT)
	(envelope-from robert@fledge.watson.org)
Received: from localhost (robert@localhost)i7FKC4JC064554;
	Sun, 15 Aug 2004 16:12:04 -0400 (EDT)
	(envelope-from robert@fledge.watson.org)
Date: Sun, 15 Aug 2004 16:12:04 -0400 (EDT)
From: Robert Watson <rwatson@freebsd.org>
X-Sender: robert@fledge.watson.org
To: John Polstra <jdp@polstra.com>
In-Reply-To: <XFMail.20040815125806.jdp@polstra.com>
Message-ID: <Pine.NEB.3.96L.1040815160330.30898Q-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: threads@freebsd.org
cc: mbr@freebsd.org
Subject: RE: thread-unsafe syslog code in libc?
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.1
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: Sun, 15 Aug 2004 20:37:36 -0000

On Sun, 15 Aug 2004, John Polstra wrote:

> The above is only to handle an unusual error case. 
> 
> There is some thread-unsafeness here, but it doesn't look like it would
> matter under normal conditions. 

So maybe we're dealing with a user space race where multiple threads
attempt to do a first syslog in parallel?

Martin -- do we know exactly what that application does threadwise to
generate this problem?

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