Minutes of the 10th April 2014 Teleconference Austin-651 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 11 April 2014 Attendees: Mark Ziegast, SHware Systems Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Andrew Josey, The Open Group Don Cragun, IEEE PASC OR Geoff Clare, The Open Group David Clissold, IBM Richard Hansen, BBN (2nd half) Joerg Schilling FOKUS Fraunhofer Mark Brown, Canonical Eric Blake, Red Hat Apologies Martin Rehak, Oracle, The Open Group OR * General news On the issues forwarded (794/800) to the Base Working Group, Andrew reported that the outcome was that the Base Working Group had decided not to sponsor. Andrew will take an action to update the bug reports and to close them. On TC2 development, Andrew is still progressing the bugs, and had made some editorial updates to the initial set of 173 bugs. He has spent some time setting up an SVN repository, and we discussed that. We decided that we would prefer to reduce the notifications possibly to once per day if that is possible - Andrew also said he needs to review if there is a better notification hook as the current one does not include URLs back to the repository. We also decided to look at enabling read only access for svn clients. Andrew reported there was progress on hearing back from IEEE on the matter of access to historical draft standards. He has received a note from our staff liaison and will report back on that for the next meeting. Mark Ziegast reported he expects to start work soon on the action to examine Open bugs for suitable Action Items for TC2 that haven't been noted as Assigned, or have been non-responsive about completion. Mark will send the results of his action to the Austin Core mailing list. * 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 * Current Business Bug 0000794: Add a function series for formatted error messages CLOSED http://austingroupbugs.net/view.php?id=794 Andrew reported that the Base Working Group has no consensus to sponsor and will close the bug. Bug #0000800: Add support for the recursive printf() format %r CLOSED http://austingroupbugs.net/view.php?id=800 Similar to 794, but the feeling was that this was the remit of the C Committee rather than POSIX. Eric has an action on fnmatch() with FNM_PATHNAME which is still open. Bug #811: precondition for mutex destruction unclear; example contradicts normative text OPEN http://www.austingroupbugs.net/view.php?id=811 We have left this item open pending further input from Dave Butenhof on supplying a new example. Bug #226: Questions on awk grammar OPEN http://austingroupbugs.net/view.php?id=226 Some feedback has been received during the week and notes added to the bug. This item remains open. Bug #701: unget[w]c() and file position after discarding push back OPEN http://austingroupbugs.net/view.php?id=701 This was discussed and Nick added the latest status to the bug: Under consideration by C. See: http://open-std.org/JTC1/SC22/WG14/www/docs/n1720.htm [^] This was discussed at the Chicago C meeting in 2013: ungetc / ungetwc and file position after discarding push back problems. Ref Austin Group Defect #701, says that "or discarding" makes no sense. Larry Jones pointed out that the Standard is correct as written because the intent is that the specified file position indicator is an intermediate state inside the file positioning function after the pushed-back characters are discarded but before the actual seek. That gives you a reliable file position from which to do the seek. It's not intended that the file positioning function doesn't set the file position indicator. Needs a Committee Response rather than a Suggested Change or possible footnote to explain why. Bill Seymour proposed the following Suggested TC. Add a footnote after "pushed-back characters" in the second sentence of 7.21.7.10p5: After the file positioning function discards the characters but before it actually does the repositioning. Add a footnote after "pushed‐back wide characters" in the second sentence of 7.29.3.10p5: After the file positioning function discards the characters but before it actually does the repositioning. After some discussion, we decided that the above words needed some editing. ACTION: Larry Jones to reword the Suggested TC footnote for DR 438. Leave OPEN Bug #832: Clarify whether field splitting applies to arithmetic expansion Accepted as Marked http://austingroupbugs.net/view.php?id=832 This item is tagged for TC2-2008. An interpretation is required. 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: Section 2.6.5 doesn't mention arithmetic expansion (which specifies when field splitting is done), but section 2.6 (where is talks about the order of word expansions) does require field splitting after arithmetic expansions. Notes to the Editor (not part of this interpretation): Change: The shell shall treat each character of the IFS as a delimiter and use the delimiters as field terminators to split the results of parameter expansion and command substitution into fields. on P2333, L74136-74137 to: The shell shall treat each character of the IFS as a delimiter and use the delimiters as field terminators to split the results of parameter expansion, command substitution, and arithmetic expansion into fields. Bug #374: malloc(0) and realloc(p,0) must not change errno on success OPEN http://austingroupbugs.net/view.php?id=374 This was discussed in the teleconference. We plan to accept these changes in spirit, but since there is overlap with several other bugs, we will wait until after TC2 has been merged into Issue 7 in order to have a clean starting point for the detailed edits. See http://open-std.org/JTC1/SC22/WG14/www/docs/dr_400.htm [^] Pipe issue from email reflector (Subject: pipe() file descriptor value ordering?) http://thread.gmane.org/gmane.comp.standards.posix.austin.general/9286 There seems to be general agreement that fildes[1] could be less than fildes[0] Maybe add a generic paragraph that fd allocation is atomic among all functions, but where a single function can allocate multiple fds (such as pipe, socketpair, recvmsg with SCM_RIGHTS,...) there is no further requirement on relations between the fds or on whether second fd can take over an fd that was not free when the first fd was allocated. The generic paragraph would mention that a single allocation uses the lowest fd at the point of the atomic check. Thus, change "two lowest" to instead "two fds are allocated". Change the ERRORS section to make it clear that no fd is consumed on failure. Perhaps this needs to be added to other multiple fd allocators? We agreed to continue on this item on the next call. Next Steps ---------- The next call is on April 17, 2014 (a Thursday) We will pick up on the discussion about pipe(). 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#