Getting this on record:

No negative comments were received to this request; the Austin Group
will therefore proceed with consideration on each of the proposed
additions.

On Thu, Aug 22, 2024 at 12:11:15PM -0500, Eric Blake wrote:
> Dear all,
> 
> Now that POSIX Issue 8 has been released, The Open Group has collected
> several requests from the Austin Group for sponsoring new APIs that
> would appear in a future revision of POSIX.  In practice this means we
> would review and approve a document containing these new API
> definitions according to The Open Group standards process.
> 
> The proposed interfaces, with more details about each, are as follows:
> 
> - The mktemp utility:
> https://austingroupbugs.net/view.php?id=1616
> Command-line support for creating temporary files and directories.
> There are several known implementations with different sets of
> options; the proposal seeks to standardize only a common subset among
> implementations (leaving other features of existing implementations as
> extensions).
> 
> - The getpeereid() function:
> https://austingroupbugs.net/view.php?id=1622
> Standardize a way to determine credentials of the process that creates
> a Unix socket.  This proposal picks up an interface present in several
> implementations.  Other similar interfaces (such as getsockopt() with
> SO_PEERCRED) should also be considered in influencing what gets
> standardized.
> 
> - The memrchr() function:
> https://austingroupbugs.net/view.php?id=1633
> A way to quickly locate the last instance of a particular byte among a
> known-length section of memory, with several instances of known
> compatible implementations.  Of note: the Austin Group notes that
> there are no plans to introduce a counterpart wmemrchr() counterpart
> unless feedback is received pointing to an existing implementation.
> 
> - The tzalloc(), mktime_z(), and other related functions:
> https://austingroupbugs.net/bug_view_page.php?bug_id=1794
> Standardize a family of functions to make it possible to do
> thread-safe access to time zone information, complementing existing
> interfaces that require global synchronization around the environment
> variable TZ.  Based on existing implementations.
> 
> - The strcasestr() and strcasestr_l() functions:
> https://austingroupbugs.net/view.php?id=1818
> Several implementations exist for case-insensitive comparisons of
> strings.  Behavior for the POSIX (or C) locale is obvious, behavior
> for other locales may be left unspecified.
> 
> - The pathconfat() function:
> https://austingroupbugs.net/view.php?id=1831
> Make it easier to query properties as if by pathconf(), but using the
> power of fd-relative queries similar to other functions in the *at()
> family (openat, mkdirat, ...).  This also makes it possible to learn
> timestamp resolutions of symlinks.
> 
> - The preadv() and pwritev() functions:
> https://austingroupbugs.net/view.php?id=1832
> Combine the best aspects of scatter-gather I/O (readv/writev) and
> random access I/O independent of the file description's offset
> (pread/pwrite).  There are several known implementations.
> 
> This is a call for any comments or objections; please respond by Sep
> 22 (either to this list or directly to me); I will compile the results
> after this 30 day window.  If no objections raised, or are properly
> addressed, then adding these interfaces will be included in the Austin
> Group workplan to be considered as part of the next revision of POSIX.
> Accepting the sponsorship of the new interfaces does not lock us into
> any specific wording proposal; there is still time to fine-tune the
> proposed requirements to better match existing practice and security
> needs.
> 
> Regards,
> Eric Blake
> 

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization:  qemu.org | libguestfs.org

Reply via email to