Minutes of the 16th May 2013 Teleconference Austin-609 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 17 May 2013 Attendees Don Cragun, PASC OR Andrew Josey, The Open Group Eric Blake, Red Hat Jim Pugsley, Oracle Geoff Clare, The Open Group Nick Stoughton, USENIX, ISO/IEC OR Joerg Schilling, Fraunhofer Society Richard Hansen, BBN Mark Brown, IBM, TOG OR * General News Mark noted that he has now added support to the allowed html constructs within the Mantis bug tracker. * 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 This item needs further investigation of existing implementations. Mark reported that AIX does not have a problem with this. Jim notes he is still looking at this. +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 This item was again left open pending further feedback. +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 Mark and Jim to report back on whether pthread_cancelstate() is async-signal-safe on AIX and Solaris. Andrew to ask Apple and HP whether pthread_cancelstate() is async-signal-safe on OS X and HP-UX. Bug 622 left open pending resolution of 615. http://austingroupbugs.net/view.php?id=622 * Current Business Bug 0000672: Necessary step(s) to synchronize filename operations on disk OPEN http://austingroupbugs.net/view.php?id=672 Geoff had completed his action, but as there is ongoing discussion on the reflector we decided to leave this item open for now. Bug 0000687: Not all filesystems support posix_fallocate Accepted as marked http://austingroupbugs.net/view.php?id=687 Geoff had completed his action and produced bugnote 1599. This item is tagged for Issue 8 At page 1426 line 47096, after this text added by 0000684: Not all file systems are capable of supporting posix_fallocate(), in which case the function will return ENOTSUP. However, if a system supports the option, there must be at least one file system that is capable of supporting this function. add: The pathconf() and fpathconf() functions can be used to determine whether a file in a particular file system supports posix_fallocate(). After page 893 line 29928 section fpathconf add: _POSIX_FALLOC _PC_FALLOC 8 Cross-volume changes to XBD... After page 440 line 14855 section unistd.h, add: _POSIX_FALLOC The posix_fallocate() function is supported by the associated file. After page 443 line 14985 section unistd.h, add: _PC_FALLOC Bug 0000690: clarify behavior when calling waitpid with SA_NOCLDWAIT OPEN http://austingroupbugs.net/view.php?id=690 Richard had completed his action to propose changes. Geoff has an action to improve the wording of the proposed change (note 1602) (completed after the meeting) Bug 0000616: mbsnrtowcs clarification Accepted as Marked http://austingroupbugs.net/view.php?id=616 This item is tagged for Issue 8 New proposed changes which match Note: 0001568... At page 1277 line 41986 after applying the changes in 0000601, change: If the input buffer ends with an incomplete character, it is unspecified whether conversion stops at the end of the previous character (if any), or at the end of the input buffer. In the latter case, a subsequent call to mbsnrtowcs() with an input buffer that starts with the remainder of the incomplete character shall correctly complete the conversion of that character. to: If the input buffer ends with an incomplete character, conversion shall stop at the end of the input buffer; a subsequent call to mbsnrtowcs() with an input buffer that starts with the remainder of the incomplete character shall correctly complete the conversion of that character. Assuming that 0000601 is implemented, at page 1278 line 42008 change FUTURE DIRECTIONS from: A future version may require that when the input buffer ends with an incomplete character, conversion stops at the end of the input buffer. to None. Bug 0000691: specification of *stat_loc values confused by XSI shading; incorrect statement of wait() behavior Accepted http://austingroupbugs.net/view.php?id=691 This item is tagged for TC2-2008 Bug 0000692: More async-signal-safe functions Accepted as marked http://austingroupbugs.net/view.php?id=692 This item is tagged for TC2-2008 An interpretation is required. Interpretation response: The standard states that various string functions are not async-signal-safe, and therefore must not be used in signal handlers or between fork and exec in a multithreaded program, and conforming applications must conform to this. However, concerns have been raised about this which are being referred to the sponsor. Rationale: Since these functions do not modify or depend on global state, there are no known implementations where these functions cannot be safely used in aysnc-signal-safe code. Notes to the Editor (not part of this interpretation): At page 494 line 16845-16879 [XSH 2.4.3 table of async-signal-safe functions], add the following in proper sorted order: ffs, htonl, htons, memccpy, memchr, memcmp, memcpy, memmove, memset, ntohl, ntohs, stpcpy, stpncpy, strcat, strchr, strcmp, strcpy, strcspn, strlen, strncat, strncmp, strncpy, strnlen, strpbrk, strrchr, strspn, strstr, strtok_r, wcpcpy, wcpncpy, wcscat, wcschr, wcscmp, wcscpy, wcscspn, wcslen, wcsncat, wcsncmp, wcsncpy, wcsnlen, wcspbrk, wcsrchr, wcsspn, wcsstr, wcstok, wmemchr, wmemcmp, wmemcpy, wmemmove, wmemset Bug 0000162: Determining System Endianess during Preprocessing Accepted as Marked http://austingroupbugs.net/view.php?id=162 An extra note was added (bug note 1610) Additionally (per 0000692), add the following interfaces in sorted order to the table of async-signal-safe functions (page 494 of Issue7+TC1): be16toh, be32toh, be64toh, htobe16, htobe32, htobe64, htole16, htole32, htole64, le16toh, le32toh, le64toh Bug 0000686: Application usage for clock() conflicts with normative text OPEN http://austingroupbugs.net/view.php?id=686 Geoff took an action on 686 to propose changes to the application usage for clock() warning about its limitations on systems that have a 32-bit integer clock_t and recommending the use of times() instead. Next Steps ---------- The next call is on May 23 2013 (a Thursday) (Andrew sends his apologies in advance) Calls are anchored on US time. This call will be for the regular 90 minutes. http://austingroupbugs.net See the calendar for the list of dialup numbers. An IRC channel will be available for the meeting irc://irc.freenode.net/austingroupbugs