Minutes of the 10 January 2013 Teleconference Austin-590 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 11 January, 2013 Attendees Mark Brown, IBM, TOG OR Don Cragun, PASC OR Andrew Josey, The Open Group Geoff Clare, The Open Group Eric Blake, Red Hat Joerg Schilling, Fraunhofer Society Jim Pugsley, Oracle Apologies Nick Stoughton, USENIX, ISO/IEC OR * General News On approvals TC1 is on the agenda for IEEE approval at the end of the month. We will need to start preparing the document for publication and generation of an update for the html version. * 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 We picked up at 633 Bug 0000633: SIGEV_THREAD delivery renders many signal interfaces unsafe OPEN http://austingroupbugs.net/view.php?id=633 This item was left open. Mark and Jim took an action to report on the following aspects of AIX and Solaris behaviour for SIGEV_THREAD event notification (from timers, AIO, etc. - the answers might be different for each): 1. What is the signal mask in the thread that is created to handle the notification? (Is it just inherited from the calling thread?) 2. When an event notification is triggered and a previous handler is still executing, do they execute a new instance of the same handler concurrently, or suppress the new notification (or something else)? Jim has reported back two meetings back (circulated to Austin Core). Mark reported that he needed more time. Action: Andrew to check in with HP and Apple on their views. Bug 0000632: Side effects of pclose on cancellation are not specified OPEN http://austingroupbugs.net/view.php?id=632 We added a note to the bug with the proposal from an earlier meeting. This is being left open for feedback. Bug 0000638: bad phrase "shall not perform the link phase and return a non-zero exit status" Accepted as Marked http://austingroupbugs.net/view.php?id=638 This item is tagged for TC2-2008. We discussed whether an interpretation was needed but decided it was not. Change: it shall not perform the link phase and return a non-zero exit status on P2494, L79799-79800 to: it shall not perform the link phase and it shall return a non-zero exit status Bug 0000637: Incomplete listing of required symbolic constants Accepted as Marked http://austingroupbugs.net/view.php?id=637 This item is tagged for TC2-2008. The recommended fix: Add on P17 after line 561: _POSIX2_C_BIND Add on P17 after Line 563: _POSIX_REGEXP Add on P17 after line 564: _POSIX_SHELL Bug 0000639: dlsym, dlclose handling of invalid handles Rejected http://austingroupbugs.net/view.php?id=639 Although some sets of interfaces in the standard do not require the system to maintain a list of active objects, some applications do depend on this behavior with shared libraries. Forcing the kernel to keep track of active shared library handles should not be a big performance hit even if the implementation just keeps a linear list of open handles. (If a system expects large numbers of shared libraries to be linked in at run time, the system can certainly optimize the search of active handles.) There isn't much difference (other than the type of object involved) in having the kernel report an EBADF error if given a bad file descriptor and having the kernel report a bad shared library handle. Although we realize that the standard I/O package does not behave this way, we know that applications sometimes pass bad stream handles to stdio routines and can't detect the error until much later. Therefore, we choose to reject this suggestion. Bug 0000623: poll should not modify fds[i].fd and fds[i].events OPEN http://austingroupbugs.net/view.php?id=623 This item was discussed but not finalized yet. It was felt that there should be some normative text stating that functions can only perform actions described in the standard, but so far we have not found it. If it is not there, we should add some text. Next Steps ---------- The next call is on January 17 2013 (a Thursday) 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.net/austingroupbugs