Re: kern/72394: [PATCH] syslog is not thread-safe

[ Available lists | Index of freebsd-standards | Month of Nov 2004 | Week of 1 Nov 2004 | Raw email | View thread | Wrap long lines | Reply | Tag ]
From
Dan Nelson <dnelson@allantgroup.com>
Date
1 Nov 2004 22:19:56
Subject
Re: kern/72394: [PATCH] syslog is not thread-safe
Message-ID
20041101221955.GA55850@dan.emsphone.com


[ Hide this part ]
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


Elapsed time: 0.098 seconds