Minutes of the 2 October 2014 Teleconference Austin-677 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 3rd October 2014 Attendees Mark Ziegast, SHware Systems Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE PASC OR Martin Rehak, Oracle, The Open Group OR Geoff Clare, The Open Group David Clissold, IBM Joerg Schilling, FOKUS Fraunhofer Eric Blake, Red Hat Matthew Dempsky Apologies Richard Hansen, BBN Andrew Josey, The Open Group * General news On the PASC PAR approval progress - still open. Don currently has the action to progress. * 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 - Open Actions Bug #851: pthread_atfork orphans handlers in unloaded shared libraries OPEN http://www.austingroupbugs.net/view.php?id=851 Action item: Andrew should try and contact to Finnbarr Murphy. (Status: Andrew has sent a query to Finnbarr via linked.in and also to his direct email - no update this week) Bug #854: requirement for additional built-in utilities to be searched for via $PATH was not and is not existing practice OPEN http://austingroupbugs.net/view.php?id=854 Action: Andrew to ask David Korn to comment on this bug and the previous email discussion of the issue (seq 21270). Action completed - awaiting response from David. Bug #859: Add posix_random family of interfaces OPEN http://austingroupbugs.net/view.php?id=859 Action on The Open Group Base WG to respond whether they will sponsor. - Bug processing Bug 0000867: typographical issue in Shell Command Language 2.6.2 Accepted as Marked http://austingroupbugs.net/view.php?id=867 This item is tagged for TC2-2008 On page 2329 lines 73947-73947 delete: (For example, ${foo-bar}xyz} would result in the expansion of foo followed by the string xyz} if foo is set, else the string "barxyz}"). After page 2330 line 74013 add: ${parameter-word} This example demonstrates the difference between unset and set to the empty string, as well as the rules for finding the delimiting close brace. foo=asdf echo ${foo-bar}xyz} asdfxyz} foo= echo ${foo-bar}xyz} xyz} unset foo echo ${foo-bar}xyz} barxyz} (Editors: Please see the online version for bolding) Bug 0000869: Concept of being "blocked" on a semaphore is not defined but needed for sem_destroy rules Reject http://austingroupbugs.net/view.php?id=869 XBD 3.76 defines a Blocked Process (or Thread) as "A process (or thread) that is waiting for some condition (other than the availability of a processor) to be satisfied before it can continue execution." By this definition, the thread is blocked by sem_wait(). Adding additional language here does not clarify the situation. Bug 0000870: Can sem_close be called when there are waiters blocked? Accepted as Marked An interpretation is required. This item is tagged for TC2-2008 Interpretation response: The standard does not speak to this issue, and as such no conformance distinction can be made between alternative implementations based on this. This is being referred to the sponsor. Rationale: There are current implementations which return mmap()ed memory and therefore a sem_close() in this situation on such implementations will result in undefined behavior. Notes to the Editor (not part of this interpretation): On page 1827 line 58866 after: The effect of subsequent use of the semaphore indicated by sem by this process is undefined. add: If any threads in the calling process are currently blocked on the semaphore, the behavior is undefined. ACTION: Andrew to start review of pending interps. Bug 0000871: Missing potential error code, EOVERFLOW Accepted as Marked http://austingroupbugs.net/view.php?id=871 This item is tagged for Issue 8 Although we agree that EAGAIN or ERANGE (as used in semop()) might be better choices for this error, at least one implementation already uses EOVERFLOW for this condition. We didn't find a compelling reason to change existing practice. Add to the sem_post() ERRORS section after P1837, L59190: [EOVERFLOW] The semaphore value would exceed {SEM_VALUE_MAX}. Next Steps ---------- The next call is on October 9, 2014 (a Thursday) 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#