bin/60477: need thread safe gethostent() and getservent()
Alfred Perlstein
alfred at FreeBSD.org
Sun Dec 21 12:30:17 PST 2003
>Number: 60477
>Category: bin
>Synopsis: need thread safe gethostent() and getservent()
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sun Dec 21 12:30:11 PST 2003
>Closed-Date:
>Last-Modified:
>Originator: Alfred Perlstein
>Release: FreeBSD 4.9-STABLE i386
>Organization:
RED, Inc.
>Environment:
System: FreeBSD freefall.freebsd.org 4.9-STABLE FreeBSD 4.9-STABLE #10: Wed Dec 10 19:46:23 PST 2003 kensmith at freefall.freebsd.org:/c/src/sys/compile/FREEFALL i386
>Description:
Hard to write thread safe networking apps without reentrant
versions of these function.
>How-To-Repeat:
>Fix:
Use thread local storage to make these safe or...
Implement gethostent_r and getservent_r, perferably from the
http://publib16.boulder.ibm.com/pseries/en_US/libs/commtrf2/gethostent_r.htm specification, although
or
http://www.qnx.com/developer/docs/qnx_6.1_docs/neutrino/lib_ref/g/gethostent_r.html
I feel that the one that Solaris and glibC offer are technically useless.
I think that making them thread safe by using thread local data
might also work reasonably well.
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-bugs
mailing list