All
Enclosed are the minutes of yesterday’s meeting
regards
Andrew
--------------
Minutes of the 9th May 2024 Teleconference Austin-1404 Page 1 of 1
Submitted by Andrew Josey, The Open Group. 10th May 2024
Attendees:
Andrew Josey, The Open Group
Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR
Don Cragun, IEEE SA OR
Geoff Clare, The Open Group
Eric Blake, Red Hat, The Open Group OR
Apologies
Tom Thompson, IEEE
Eric Ackermann, CISPA
Mark Ziegast, SHware Systems Dev
* General news
The general news is unchanged.
The IEEE Revcom committee met on May 6 to consider approval of draft 4.1.
We have yet to hear the result.
After approval we can moved forward to complete the frontmatter
and proceed to publication, and the html conversion.
The ISO/IEC ballot closes on June 28.
* Current Business
1797: strftime "%s" should be able to examine tm_gmtoff OPEN
https://austingroupbugs.net/bug_view_page.php?bug_id=1797
We will continue this item next time that Paul is available (expected in April).
Bug 1817: lseek(2) - "size of a file" undefined Accepted as Marked
https://austingroupbugs.net/view.php?id=1817
Proposed interpretation (review timer to start after approval of
issue 8), using draft 4.0 line numbers .
Interpretation response:
The standard states that the posix_getdents() function starts reading
at the current file offset in the open file description associated
with fildes, and conforming implementations must conform to this.
However, concerns have been raised about this which are being
referred to the sponsor.
Rationale:
Elsewhere the standard makes allowances for implementations where
directory streams are not implemented using a file descriptor, but
this was not extended to the new posix_getdents() function when it
was added.
Notes to the Editor (not part of this interpretation):
After page 920 line 31407 section fdopendir(), add a new paragraph:
If the file descriptor specified by fd is associated with an
open file description on which posix_getdents() has previously
been used, or for which any associated file descriptor is already
associated with a directory stream, the behavior is unspecified.
After page 1567 line 52616 section posix_getdents():
The behavior is unspecified if lseek() is used to set the file
offset to a value other than zero or a value returned by a
previous call to lseek() on the same open file description.
add these sentences:
The behavior is unspecified if calls to posix_getdents() are
made on different file descriptors that refer to the same open
file description (for example, before and after a file descriptor
is inherited across fork() or the exec family of functions, or
is duplicated using dup() or fcntl()), unless lseek() is used
to set the file offset to zero in between the calls to
posix_getdents(). A single exception to this condition is that
after a call to fork(), either the parent or child (but not
both) can continue processing the directory using posix_getdents().
Likewise, the behavior is unspecified if in between two calls
to posix_getdents() on one file descriptor, the file offset is
altered by a call made on a different file descriptor that
refers to the same open file description.
At page 1568 line 52626 section posix_getdents(), change:
If a sequence of calls to posix_getdents() is made that reads
from offset zero to end-of-file and a file is removed from or
added to the directory between the first and last of those
calls, whether the sequence of calls returns an entry for that
file is unspecified.
to:
If a sequence of calls to posix_getdents() is made that reads
from offset zero to end-of-file and a directory entry is removed
from or added to the directory between the first and last of
those calls, whether the sequence of calls returns that directory
entry is unspecified.
After page 1571 line 52771 section posix_getdents(), add a new
paragraph to RATIONALE:
The restrictions on the use of different file descriptors that
refer to the same open file description are needed in order to
enable implementations where directory streams are not implemented
using a file descriptor to maintain some internal state related
to a particular file descriptor.
At page 1858 line 61304, section readdir(), change:
If a file is removed from or added to the directory after the
most recent call to opendir() or rewinddir(), whether a subsequent
call to readdir() returns an entry for that file is unspecified.
to:
If a directory entry is removed from or added to the directory
after the most recent call to opendir() or rewinddir(), whether
a subsequent call to readdir() on that directory stream returns
that directory entry is unspecified. For all other directory
entries in the directory that existed at the time the directory
stream was opened or rewound and which have not been removed,
successive calls to readdir() on that directory stream shall
return each such directory entry exactly once before reporting
that the end of the directory has been reached, provided that
there are no intervening calls to seekdir() and no unspecified
behavior caused by performing an operation on an open file
description associated with the directory.
At page 1858 line 61319 section readdir(), change:
the result is undefined.
to:
the result is unspecified.
At page 1859 line 61332 section readdir(), change:
The readdir_r() function shall not return directory entries
containing empty names.
If a file is removed from or added to the directory after the
most recent call to opendir() or rewinddir(), whether a subsequent
call to readdir_r() returns an entry for that file is unspecified.
to:
The readdir_r() function shall not return directory entries
containing empty names. If entries for dot or dot-dot exist,
one entry shall be returned for dot and one entry shall be
returned for dot-dot; otherwise, they shall not be returned.
If a directory entry is removed from or added to the directory
after the most recent call to opendir() or rewinddir(), whether
a subsequent call to readdir_r() on that directory stream returns
that directory entry is unspecified. For all other directory
entries in the directory that existed at the time the directory
stream was opened or rewound and which have not been removed,
successive calls to readdir_r() on that directory stream shall
return each such directory entry exactly once before reporting
that the end of the directory has been reached, provided that
there are no intervening calls to seekdir() and no unspecified
behavior caused by performing an operation on an open file
description associated with the directory.
Bug 1818: Add strcasestr() & strcasestr_l() OPEN
https://austingroupbugs.net/view.php?id=1818
Action: Eric B to ask The Open Group if they are willing to sponsor
these functions for Issue 9.
Bug 1820: The impact of changing NF should be stated OPEN
https://austingroupbugs.net/view.php?id=1820
We started on this item. Notes are in the etherpad.
We will continue on this item next time.
Next Steps
----------
The next call is on:
Mon 2024-05-13 (WEBEX meeting - general bugs)
Thu 2024-05-16 (WEBEX meeting - general bugs)
The calls are for 90 minutes
Calls are anchored on US time. (8am Pacific)
Please check the calendar invites for dial in details.
Bugs are at:
https://austingroupbugs.net
An etherpad is usually up for the meeting, with a URL using the date format as
below:
https://posix.rhansen.org/p/20xx-mm-dd
(For write access this uses The Open Group single sign on,
for those individuals with gitlab.opengroup.org accounts.
Please contact Andrew if you need to be setup)
--------
Andrew Josey The Open Group
Austin Group Chair
Email: [email protected]
Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England
To learn how we maintain your privacy, please review The Open Group Privacy
Statement at http://www.opengroup.org/privacy.
To unsubscribe/opt-out from this mailing list login to The Open Group
collaboration portal at
https://collaboration.opengroup.org/operational/portal.php?action=unsub&listid=2481
