Minutes of the 19th June 2014 Teleconference Austin-660 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 20th June 2014 Attendees: Don Cragun, IEEE PASC OR Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Andrew Josey, The Open Group Geoff Clare, The Open Group Richard Hansen, BBN Martin Rehak, Oracle David Clissold, IBM Joerg Schilling, FOKUS Fraunhofer Eric Blake, Red Hat Apologies: Mark Brown, * General news Andrew had circulated a cleaned up TC2 PAR to the core team, together with the PASC PMC evaluation criteria. It was agreed that this was now ready to send onto the PASC SEC for their approval. Action: Andrew to send PAR and PMC evaluation criteria for TC2 to the PASC SEC (completed after the meeting) Geoff has continued to update the TC2 bugs in the SVN repository, and has now completed breaking them all out to their pages. A new work in progress draft has been checked into the repository. Action: Andrew also to send a copy of the work in progress draft to the core team (completed after the meeting) * Outstanding actions +Bug 0000251: Forbid newline, or even bytes 1 through 31 (inclusive), in filenames OPEN http://austingroupbugs.net/view.php?id=251 Don has an action to produce a proposal. +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 Jim had provided additional information in bugnote 1627. This was discussed and Jim took an action to provide further information. +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 0000517: EBNF support OPEN http://austingroupbugs.net/view.php?id=517 Action on Joerg to look at this. +Bug 0000633: SIGEV_THREAD delivery renders many signal interfaces unsafe OPEN http://austingroupbugs.net/view.php?id=633 We noted that feedback has settled down on the mailing list, and will discuss next session. +Bug 0000657: Conditions under which fmemopen() write a NUL to the buffer are insufficiently specified OPEN http://austingroupbugs.net/view.php?id=657 Eric has an action to propose wording to clarify the behavior for fmemopen(), and also to contact the glibc developers to get their feedback. +Bug 0000658: Undefined/unspecified behavior clauses in description of open have race conditions OPEN http://austingroupbugs.net/view.php?id=658 It was noted that there is some overlap with changes in TC1. Eric took an action to update the proposal to resolve the overlaps appropriately. +Bug 0000615: pthread_setcancelstate should be async-signal-safe OPEN http://austingroupbugs.net/view.php?id=615 We now have reports on AIX and Apple. Jim to report back on whether pthread_cancelstate() is async-signal-safe on Solaris. Andrew to ask HP whether pthread_cancelstate() is async-signal-safe on HP-UX. +Bug 0000672: Necessary step(s) to synchronize filename operations on disk OPEN http://austingroupbugs.net/view.php?id=672 Geoff has a new proposed resolution in note 1618. Decided to solicit input from FS developers. Eric to go to Linux, David to AIX and Jim to Solaris. Jim has completed his action (see bugnote 1691). Andrew should chase HP and Apple for input. +Bug 0000663: Specification of str[n]casecmp is ambiguous reopened http://austingroupbugs.net/view.php?id=663 Action on David to follow up with the IBM developers about the EBCDIC collation sequence. Bug 696 either NAME_MAX shouldn't be optional, or readdir_r() needs clarification http://www.austingroupbugs.net/view.php?id=696 Don has an action to propose a resolution. Bug 0000721: Internal storage vs static storage OPEN http://austingroupbugs.net/view.php?id=721 This item is still open. Bug 0000375: Extend test/[...] conditionals: ==, <, >, -nt, -ot, -ef OPEN http://austingroupbugs.net/view.php?id=375 This is still left open due to discussions pending on the reflector. Bug 0000789: Add set -o pipefail OPEN http://austingroupbugs.net/view.php?id=789 * Current Business Bug #845: Two variables not included in System Interfaces Accepted as Marked http://www.austingroupbugs.net/view.php?id=845 This item was tagged for Issue 8 On page 475 on line 16090 add the prefix: in6addr_ keeping IP6 shading on the entire line. After page 1122 insert a new page (with the SYNOPSIS IP6 shaded): NAME in6addr_any, in6addr_loopback --- IPv6 address variables SYNOPSIS #include const struct in6_addr in6addr_any; const struct in6_addr in6addr_loopback; DESCRIPTION The in6addr_any variable is initialized by the system to contain the wildcard IPv6 address (::). The in6addr_loopback variable is initialized by the system to contain the loopback IPv6 address (::1). RETURN VALUE None. ERRORS No errors are defined. EXAMPLES None. APPLICATION USAGE None. RATIONALE These variables were only described on the XBD page in earlier versions of this standard. FUTURE DIRECTIONS None. SEE ALSO bind(), connect() XBD CHANGE HISTORY First released in Issue 8. Derived from Issue 7 XBD . Bug #811: precondition for mutex destruction unclear; example contradicts normative text Accepted as Marked http://www.austingroupbugs.net/view.php?id=811 This item is tagged for TC2-2008. On page 1643 line 53249 section pthread_mutex_destroy() change from: Attempting to destroy a locked mutex or a mutex that is referenced (for example, while being used in a pthread_cond_timedwait() or pthread_cond_wait()) by another thread results in undefined behavior. to: Attempting to destroy a locked mutex, or a mutex that another thread is attempting to lock, or a mutex that is being used in a pthread_cond_timedwait() or pthread_cond_wait() call by another thread, results in undefined behavior. On page 1647 lines 53424-53425 change: A mutex can be destroyed immediately after it is unlocked. For example, consider the following code: to: A mutex can be destroyed immediately after it is unlocked. However, since attempting to destroy a locked mutex, or a mutex that another thread is attempting to lock, or a mutex that is being used in a pthread_cond_timedwait() or pthread_cond_wait() call by another thread, results in undefined behavior, care must be taken to ensure that no other thread may be referencing the mutex. On page 1647 delete lines 53426-53444. Bug 0000846: sigaction errors has probably left over artefact Duplicate of 491 http://www.austingroupbugs.net/view.php?id=846 This bug is a duplicate of 0000491 Bug 0000847: open(O_CREAT), directories, and EISDIR OPEN http://www.austingroupbugs.net/view.php?id=847 Some notes were added to the bug (see note 2268) and discussion will continue next time. Next Steps ---------- The next call is on June 26, 2014 (a Thursday) There will be no call on July 3rd. Calls are anchored on US time. (8am Pacific) This call will be for the regular 90 minutes. http://austingroupbugs.net An IRC channel will be available for the meeting irc://irc.freenode.net/austingroupbugs An etherpad is usually up for the meeting, with a URL using the date format as below: http://posix@posix.rhansen.org:9001/p/201x-mm-dd password=2115756#