Minutes of the 6 March 2014 Teleconference Austin-647 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 8 March 2014 Attendees: Mark Ziegast, SHware Systems Eric Blake, Red Hat Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Andrew Josey, The Open Group Joerg Schilling FOKUS Fraunhofer Don Cragun, IEEE PASC OR Geoff Clare, The Open Group Martin Rehak, Oracle, The Open Group OR David Clissold, IBM Mark Brown, Canonical Apologies: Richard Hansen, BBN David Wheeler, IDA * General news On the issues forwarded (794/800) to the Base Working Group, Andrew reported that he will be progressing that in the Base WG to come up with a consolidated position to bring back. He will start that this week. On TC2 development, Andrew reported he was progressing and was on bug 125 out of 173 in his current queue. Andrew reported he had still not heard back yet from the IEEE staff liaison on the matter of access to historical draft standards, and will ping them. * 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 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. 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 Bug 0000794: Add a function series for formatted error messages OPEN http://austingroupbugs.net/view.php?id=794 Martin has completed his action to forward to The Open Group Base Working group to see if they would be willing to sponsor this proposal for new interfaces. Bug #0000800: Add support for the recursive printf() format %r OPEN http://austingroupbugs.net/view.php?id=800 Joerg has an action to write a new proposal. Martin has also forwarded this to The Open Group Base Working group for their consideration. * Current Business Eric reported that his action on fnmatch() with FNM_PATHNAME is still open. He has been testing on glibc and wants to test on soem other platforms. Andrew stated that the editors had identified some additional changes to bug 685 for TC2, and a note has been attached to the bug. Bug #811: precondition for mutex destruction unclear; example contradicts normative text OPEN http://www.austingroupbugs.net/view.php?id=811 Action: Andrew to contact Dave Butenhof for his input on this item, with special attention to the paragraph commencing line 53441. Bug #812: Incorrect reference to ed command Accept http://www.austingroupbugs.net/view.php?id=812 This item is tagged for TC2-2008. Bug #813: Utility numeric argument syntax requirements ambiguous Accepted as Marked http://www.austingroupbugs.net/view.php?id=813 An interpretation is required. This item is tagged for TC2-2008 Interpretation response: The standard is unclear on this issue, and no conformance distinction can be made between alternative implementations based on this. This is being referred to the sponsor. Rationale: The normative requirement in XCU 1.5 does not match the syntax utility guidelines which suggest very large values may be supported but are not required to be. Notes to the Editor (not part of this interpretation): On page 214, after line 7104, add a new bullet * When the utility description states that the number is a file size-related value (such as a file size or offset, line number, or block count), numerals in the range 0 to the maximum file size supported by the implementation are syntactically recognized as numeric values (see XCU 1.5 Considerations for Utilities in Support of Files of Arbitrary Size). Where negative values are permitted, any value in the range -(maximum file size) to the maximum file size is accepted. Bug #814: unclear behavior when 'size' keyword deleted or overriden OPEN http://www.austingroupbugs.net/view.php?id=814 We commenced looking at this bug, and will continue next week. We are leaning towards adding a note saying that the results are undefined if you tell pax to use values that override data that determines the positions of files in an archive. Next Steps ---------- The next call is on March 13, 2014 (a Thursday) Apologies in advance from Joerg, Mark B, and David - Andrew will act as moderator and bring up the bridge. Calls are anchored on US time. (8am Pacific) ( note that the US will be on summer time next week) 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#