Minutes of the 19th July 2018 Teleconference Austin-876 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 20th July 2018 Attendees: Mark Ziegast, SHware Systems Dev. Joerg Schilling, FOKUS Fraunhofer Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE PASC OR Geoff Clare, The Open Group David Clissold, IBM Andrew Josey, The Open Group Eric Blake, Red Hat Apologies: Richard Hansen, Google Martin Rehak, Oracle, The Open Group OR * General news No news * Outstanding actions ( Please note that this section has been flushed to shorten the minutes - to locate the previous set of outstanding actions, look to the minutes from 9 March 2018 and earlier) * Current Business Bug 1077: Recommend support for wide-character regcomp and regexec and/or specify multi-byte behavior OPEN http://austingroupbugs.net/bug_view_page.php?bug_id=1077 Andrew has completed the action to ping his Apple contact and is awaiting a reply. Bug 1114: Clarify if fork preserves thread resources Accepted as Marked http://austingroupbugs.net/view.php?id=1114 This item is tagged for TC3-2008. On page 899 line 30368 section fork(), change APPLICATION USAGE from: None. to: When a multi-threaded process calls fork(), although all memory that is addressable in the calling thread remains addressable in the child, there is no guarantee that the contents of thread-specific memory, such as stacks or thread-local storage, that was specific to other threads in the parent will still be the same in the child. This is because such memory could be treated as available in the child given that the threads it related to do not exist in the child, and consequently the processing performed in the child before fork() returns could make use of that memory. Therefore applications should avoid using in the child any pointers to thread-specific memory that were passed to the calling thread from other threads in the parent. Bug 1115: Lock acquisition state after pthread_mutex_lock with EOWNERDEAD Accepted as Marked http://austingroupbugs.net/view.php?id=1115 This item is tagged for TC3-2008 On page 1672 line 54500 change: If mutex is a robust mutex and the owning thread terminated while holding the mutex lock, a call to pthread_mutex_lock() may return the error value [EOWNERDEAD] even if the process in which the owning thread resides has not terminated. In these cases, the mutex is locked by the thread but the state it protects is marked as inconsistent. to: If mutex is a robust mutex and the owning thread terminated while holding the mutex lock, a call to pthread_mutex_lock() may return the error value [EOWNERDEAD] even if the process in which the owning thread resides has not terminated. In these cases, the mutex shall be locked by the calling thread but the state it protects is marked as inconsistent. Bug 1116: References to old options Accepted http://austingroupbugs.net/view.php?id=1116 This item is tagged for TC3-2008 Bug 1117: Use of "implementation-defined" in command -v / -V Accepted http://austingroupbugs.net/view.php?id=1117 This item is tagged for TC3-2008 Bug 1118: Clarify meaning of "file lock" OPEN http://austingroupbugs.net/view.php?id=1118 This item will be continued on the next call. Next Steps ---------- The next call is on July 26th 2018 (a Thursday) Apologies in Advance: Andrew Josey (2018-07-26, 2018-08-02, 2018-08-09, 2018-08-23) Martin Rehak (until 2018-08-02) Calls are anchored on US time. (8am Pacific) This call will be for the regular 90 minutes. http://austingroupbugs.net An etherpad is usually up for the meeting, with a URL using the date format as below: https://posix.rhansen.org/p/201x-mm-dd username=posix password=2115756#