Minutes of the 10 October 2012 Teleconference Austin-581 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 11 October, 2012 Attendees Don Cragun, PASC OR Andrew Josey, The Open Group Geoff Clare, The Open Group Eric Blake, Red Hat Mark Brown, IBM, TOG OR Joerg Schilling, Fraunhofer Society Nick Stoughton, USENIX, ISO/IEC OR Apologies Jim Pugsley, Oracle * General News There was no change in status on the outstanding approvals. * Old Business +Bug 0000561: NUL-termination of sun_path in Unix sockets OPEN http://austingroupbugs.net/view.php?id=561 Eric has an action to update the proposal. +Bug 0000573: Please add '+' to the portable filename character set OPEN http://austingroupbugs.net/view.php?id=573 Joerg has an action to prepare a proposed change. +Bug 0000592: consistent use of struct timespec OPEN http://austingroupbugs.net/view.php?id=592 This item needs further investigation of existing implementations. Mark reported that AIX does not have a problem with this. Jim notes he is still looking at this. +Bug 0000598: OH shading and new interfaces OPEN http://austingroupbugs.net/view.php?id=598 Eric has an action to propose a new solution with self-contained headers. Bug 0000576: No format specifiers for several types OPEN http://austingroupbugs.net/view.php?id=576 Bug 0000599: Reserved "no thread" value for pthread_t A/M Issue 8 Bug 0000517: EBNF support OPEN http://austingroupbugs.net/view.php?id=517 It was agreed that we need Joerg's input on this item and have left it open for now. Andrew took an action on the 12 September call to notify Joerg (completed after the meeting). * Current Business Bug 0000611: Interaction of exit with stdio stream locking is not specified Accepted as marked http://austingroupbugs.net/view.php?id=611 This item was reopened. This item is tagged for TC2-2008. An interpretation is required. Interpretation response: The standard clearly states that all functions that reference (FILE *) objects (except those with names ending in _unlocked) shall behave as if they use flockfile() and funlockfile() internally to obtain ownership of these (FILE *) objects, and conforming implementations must conform to this. Rationale: The internal stream lock protects the data in the FILE structure. All functions, except those with names ending in _unlocked, which modify these data must obtain the stream lock before they do so, and that includes exit(). Notes to the Editor (not part of this interpretation): After page 859 line 28523 section flockfile() add a new paragraph to APPLICATION USAGE: A call to exit() can block until locked streams are unlocked because a thread having ownership of a (FILE *) object blocks all function calls that reference that (FILE *) object (except those with names ending in _unlocked) from other threads, including calls to exit(). Bug 0000619: Update RFCs listed in mailx rationale Accepted http://austingroupbugs.net/view.php?id=619 The working group noted the discussion on the mailing list about mbox format that arose from bug 619 and decided no change to the standard is needed. Bug 0000612: dirname of "usr/" or "/" are not clear OPEN http://austingroupbugs.net/view.php?id=612 Don had completed his previous action, but took a new action to propose a new resolution after discussions on this weeked. Action on Nick to file a new bug on the dirname utility rationale. Bug 0000609: It is not clear what threads are considered blocked with respect to a call to pthread_cond_signal() or pthread_cond_broadcast() OPEN http://austingroupbugs.net/view.php?id=609 Dave Butenhof had provided input and this was added as note 1396. This item was left open for now. Bug 0000610: Possible race condition in requirements of exit and their interaction with threads. OPEN http://austingroupbugs.net/view.php?id=610 The working group discussed bug 610 and reached consensus, but ran out of time to update the bug in Mantis. The consensus was that applications should ensure that when one thread calls exit() there are no other threads that might still be using stdio streams. If the timing is such that one of these threads tries to use a stdio stream after exit() has closed it, the behavior is undefined. Threads can only be used transparently as an implementation detail in libraries if the design of the library's API is such that the application can be sure the library is in an "exit-safe" stable condition before calling exit(). Next Steps ---------- The next call is on October 17. This call will be for the regular 90 minutes. http://austingroupbugs.net See the calendar for the list of dialup numbers. An IRC channel will be available for the meeting irc://irc.freenode.org/austingroupbugs