Minutes of the 1st August 2013 Teleconference Austin-620 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 2nd August 2013 Attendees Don Cragun, PASC OR Geoff Clare, The Open Group Eric Blake, Red Hat Joerg Schilling, Fraunhofer Society David Clissold, IBM Mark Brown, IBM Andrew Josey, The Open Group Jim Pugsley, Oracle , The Open Group OR (acting) Richard Hansen, BBN Apologies Nick Stoughton, USENIX, ISO/IEC OR * General news Don reported he had received an integration plan for the merger of 1003.26 into the specification , to be targeted in Issue 8. He will circulate that soon. Andrew reported that Jim Pugsley was acting as The Open Group Organization Representative, and that he will have that ratified shortly. * Outstanding actions +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 622 left open pending resolution of 615. http://austingroupbugs.net/view.php?id=622 +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. * Current Business Bug 0000721: Internal storage vs static storage OPEN http://austingroupbugs.net/view.php?id=721 This item is still open. Bug 0000267: time (keyword) Accepted as marked. http://austingroupbugs.net/view.php?id=627 An item brought forward from last week was to decide how to update bug 267 so that it does not undo the bug 723 TC2 change when it is applied in Issue 8. An extra note was added to the bug, note 1692, to clarify instructions to the editors. No other change was made to the bug report. Bug 0000592: consistent use of struct timespec Accepted http://austingroupbugs.net/view.php?id=592 This item is tagged for Issue 8 Bug 0000724: mktime() tm_yday contradiction Accepted as Marked http://austingroupbugs.net/view.php?id=724 This item is tagged for TC2-2008 At page 1316 line 43515 change: The original values of the tm_wday and tm_yday components of the structure are ignored, and the original values of the other components are not restricted to the ranges described in . to: The original values of the tm_wday and tm_yday components of the structure shall be ignored, and the original values of the other components shall not be restricted to the ranges described in . At page 1316 line 43526 change: where the names in the structure and in the expression correspond to: where the names other than tm_yday in the structure and in the expression correspond, and the tm_yday value used in the expression is the day of the year from 0 to 365 inclusive, calculated from the other tm structure members specified in (excluding tm_wday). (This all follows a "shall", so present tense is okay.) At page 1316 line 43529 change: and the other components are set to represent the specified time to: and the other components shall be set to represent the specified time Bug 0000726: There's an extra period at the end of item 1 Accepted http://austingroupbugs.net/view.php?id=726 This item is tagged for TC2-2008. We should let the editors fix as they see fit. Bug 0000725: No EFAULT error code is specified even though pthread_setcancel*() take a pointer argument. Rejected http://austingroupbugs.net/view.php?id=725 This request is rejected. To expand on Note: 0001690, EFAULT is listed as a defined error (see XBD , page 235 line 7755; XSH 2.3 page 483 line 16408), but it is not referenced in the error list of any existing function. Adding it as a may fail for just pthread_setcancel*() would be inappropriate - if we added it, we would have to audit ALL interfaces where it would need to be added. See also XSH 2.3 (page 481 line 16312): "Implementations may support additional errors not included in this list," which gives implementations the right to return EFAULT even though the standard does not list it, and XRAT B.2.3 (page 3532 line 119487) "Attempting to infer the quality of an implementation based on whether it detects optional error conditions is not useful." ... "Some implementations cannot reliably detect an invalid address." Furthermore, per XSH 2.1.1 (page 471 line 15965), "If an argument to a function has an invalid value (such as a value outside the domain of the function, or a pointer outside the address space of the program, or a null pointer), the behavior is undefined." We cannot specify EFAULT as a behavior of something that is already declared as undefined behavior, although an implementation is free to add this as a quality of implementation extension. Bug 0000727: Missing %b mention in printf utility remark about errors Acepted as Marked http://austingroupbugs.net/view.php?id=727 This item is tagged for TC2-2008 At page 3076 line 102538 (XCU printf EXTENDED DESCRIPTION), change "a string that may contain" to "a string that can contain" At page 3076 line 102558, change "Any extra c or s conversion" to "Any extra b, c, or s conversion" At page 3077 line 102582, change "completely used for a c or s conversion" to "completely used for a b, c, or s conversion" Next Steps ---------- The next call is on August 8, 2013 (a Thursday) Calls are anchored on US time. 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