Minutes of the 21 May 2015 Teleconference Austin-709 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 22 May 2015 Attendees: Andrew Josey, The Open Group Don Cragun, IEEE PASC OR Joerg Schilling, FOKUS Fraunhofer Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Mark Ziegast, SHware Systems Geoff Clare, The Open Group Eric Blake, Red Hat Richard Hansen, BBN Martin Rehak, Oracle Apologies David Clissold, IBM Roger Faulkner, Oracle, The Open Group OR * General news None. * Outstanding actions ( Please note that I have flushed this section to shorten the minutes - to locate the last set of outstanding actions, look to the minutes from 26 Feb 2015) Bug 0000887: printf and other functions appear many times in search results OPEN http://austingroupbugs.net/view.php?id=887 Andrew is investigating. Bug 0000900: add qsort_r OPEN http://austingroupbugs.net/view.php?id=900 The consensus was that its a good idea to add the suggested interface. The usual requirements regarding a sponsor for a new interface apply. Action: Open Group OR , to ask the Base WG if they wish to sponsor the additional qsort interface proposed here. Bug 0000901: reserve _POSIX* shell option namespace for future use OPEN http://austingroupbugs.net/view.php?id=901 The forward plan for this bug remains as before: Richard: file a new bug report with a concrete feature that would use the _POSIX* namespace (as motivation for reserving set -o _POSIX*) All: debate the proposed feature. If it's something we want, then revisit bug #901. If not, close bug #901. Bug 0000922: Implementations should be allowed to change/remove implementation-defined environment variables OPEN http://austingroupbugs.net/view.php?id=922 This item remains open. Action on Eric: propose wording for Issue 8 to add secure_getenv(), and make it clear that deleting from environment without explicit request is not compliant, but ignoring is fine. For Issue 7 TC 2: Create new bug to add additional conditions on what makes TMPDIR valid, vs. undefined behavior; also add future directions to getenv() to mention secure_getenv() * Current Business Bug #939: Clarify getaddrinfo() hints initialisation Accepted as Marked http://austingroupbugs.net/view.php?id=939 This item is tagged for TC2-2008 On Page: 924 Line: 31149 Section: freeaddrinfo(), in the DESCRIPTION section, change from: In this hints structure every member other than ai_flags, ai_family, ai_socktype, and ai_protocol shall be set to zero or a null pointer. to: The application shall ensure that each of the ai_addrlen, ai_addr, ai_canonname, and ai_next members, as well as each of the non-standard additional members, if any, of this hints structure is initialized. If any of these members has a value other than the value that would result from default initialization, the behavior is implementation-defined. 0000934: Requirement for zeroing the sockaddr_in and sockaddr_un structures. Accepted as marked http://austingroupbugs.net/view.php?id=934 This item is tagged for TC2-2008 An interpretation is required Interpretation response: The standard clearly states that applications need not initialize non-standard members of the sockaddr_in and sockaddr_un structures, and conforming implementations must conform to this. Rationale: Historically some applications initialize just the standard members, and some initialize the whole structure (using default initialization or memset()). There may be applications which do the latter for sockaddr_in and then rely on the zero value of the sin_family member being set to AF_UNSPEC. Therefore the standard should require that AF_UNSPEC has the value 0. Notes to the Editor (not part of this interpretation): On Page: 306 Line: 10238 Section: , change from: The sockaddr_in6 structure shall be set to zero by an application prior to using it, since implementations are free to have additional, implementation-defined fields in sockaddr_in6. to: Prior to calling a function in this standard which reads values from a sockaddr_in6 structure (for example, bind() or connect()), the application shall ensure that all members of the structure, including any additional non-standard members, if any, are initialized. If the sockaddr_in6 structure has a non-standard member, and that member has a value other than the value that would result from default initialization, the behavior of any function in this standard that reads values from the sockaddr_in6 structure is implementation-defined. All functions in this standard that return data in a sockaddr_in6 structure (for example, getaddrinfo() or accept()) shall initialize the structure in a way that meets the above requirements, and shall ensure that each non-standard member, if any, has a value equal to the value that would result from default initialization. On Page: 309 Line: 10323 change APPLICATION USAGE from: None. to: Although applications are required to initialize all members (including any non-standard ones) of a sockaddr_in6 structure, the same is not required for the sockaddr_in structure, since historically many applications only initialized the standard members. Despite this, applications are encouraged to initialize sockaddr_in structures in a manner similar to the required initialization of sockaddr_in6 structures. On page 388 after line 13000 insert the following new paragraph: The value of AF_UNSPEC shall be 0. On page 406 after line 13620 (sys/un.h APPLICATION USAGE) insert the following new paragraph: Although applications are required to initialize all members (including any non-standard ones) of a sockaddr_in6 structure (see ), the same is not required for the sockaddr_un structure, since historically many applications only initialized the standard members. Despite this, applications are encouraged to initialize sockaddr_un structures in a manner similar to the required initialization of sockaddr_in6 structures. Bug #936: fprintf() & fscanf() should reference macros Accepted as Marked http://austingroupbugs.net/bug_view_page.php?bug_id=936 This item is tagged for TC2-2008 Add to the SEE ALSO section for the following functions: fprintf() page 912 line 30677 fscanf() page 944 line 31867 fwprintf() page 988 line 33389 fwscanf() page 998 line 33749 Bug #937: Application definition is missing text about interactive users Accepted http://austingroupbugs.net/view.php?id=937 This item is tagged for TC2-2008 Bug #940: all 0 bits should be a null pointer on POSIX systems OPEN http://austingroupbugs.net/view.php?id=940 We started discussing this item and will continue it on the next call. Next Steps ---------- The next call is on May 28, 2015 (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#