From owner-freebsd-bugs@FreeBSD.ORG  Mon Nov  1 22:19:56 2004
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 9AAED16A4CE; Mon,  1 Nov 2004 22:19:56 +0000 (GMT)
Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 4CC4243D3F; Mon,  1 Nov 2004 22:19:56 +0000 (GMT)
	(envelope-from dan@dan.emsphone.com)
Received: (from dan@localhost)
	by dan.emsphone.com (8.12.11/8.13.1) id iA1MJtI0083241;
	Mon, 1 Nov 2004 16:19:55 -0600 (CST)
	(envelope-from dan)
Date: Mon, 1 Nov 2004 16:19:55 -0600
From: Dan Nelson <dnelson@allantgroup.com>
To: Mark Linimon <linimon@FreeBSD.org>
Message-ID: <20041101221955.GA55850@dan.emsphone.com>
References: <200410300716.i9U7Gi48004946@freefall.freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200410300716.i9U7Gi48004946@freefall.freebsd.org>
X-OS: FreeBSD 5.3-BETA7
X-message-flag: Outlook Error
User-Agent: Mutt/1.5.6i
cc: freebsd-bugs@FreeBSD.org
cc: freebsd-standards@FreeBSD.org
Subject: Re: kern/72394: [PATCH] syslog is not thread-safe
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Nov 2004 22:19:56 -0000

In the last episode (Oct 30), Mark Linimon said:
> Synopsis: [PATCH] syslog is not thread-safe
> 
> Responsible-Changed-From-To: freebsd-standards->freebsd-bugs
> Responsible-Changed-By: linimon
> Responsible-Changed-When: Sat Oct 30 07:15:43 GMT 2004
> Responsible-Changed-Why: 
> This sounds more like a kern bug than something for the standards folks.
> 
> http://www.freebsd.org/cgi/query-pr.cgi?pr=72394

Well, I guess the "unp_connect" message is a kernel bug, but that's a
very minor part of the PR, and is marked with an "XXXRW: Temporary
debugging printf" comment anyway.

The larger issue is the lack of locking in the syslog family of libc
functions, which POSIX requires.

-- 
	Dan Nelson
	dnelson@allantgroup.com