All
Enclosed are the minutes of today’s meeting
regards
Andrew
-------------
Minutes of the 22nd August 2022 Teleconference Austin-1250 Page 1 of 1
Submitted by Andrew Josey, The Open Group. 22nd August 2022
Attendees:
Don Cragun, IEEE PASC OR
Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR
Eric Ackermann, HPI, University of Potsdam
Eric Blake, Red Hat, The Open Group OR
Geoff Clare, The Open Group
Andrew Josey, The Open Group
Apologies
Tom Thompson, IEEE
* General news
This was a call dedicated to general bugs.
As a reminder we agreed previously that there will be NO meetings
on 2022-08-29, 2022-09-05 (due to holidays in the UK and US
respectively)
* Current Business
Bug 1122: POSIX should include gettext() and friends OPEN
and https://posix.rhansen.org/p/gettext_draft
Also https://austingroupbugs.net/file_download.php?file_id=64&type=bug
Geoff's addition to XRAT appendix E and cancellation points lists have been
noted to date.
A new PDF will be needed, but we will continue to wait for more comments first.
To be discussed again when more comments are raised.
Bug 1560: clarify wording of command substitution
https://austingroupbugs.net/view.php?id=1560
Leave this and related bugs 1561 and 1564 open awaiting reviews/discussion.
Bug 1273: glob()'s GLOB_ERR/errfunc and non-directory files OPEN
https://austingroupbugs.net/view.php?id=1273
We will leave this open awaiting feedback.
Bug 768: add "fd-private" POSIX locks to spec OPEN
https://austingroupbugs.net/view.php?id=768
Linux has now had OFD locks for several years, and more code in the
wild is starting to use it - so we have existing practice (see note
2508)
https://www.gnu.org/software/libc/manual/html_mono/libc.html#Open-File-Description-Locks
Starting point of resolution at https://posix.rhansen.org/p/bug768
AI to EricB - take the GNU documentation and turn it into a desired action
Bug 739: CX requirements for strftime seem to conflict with ISO C OPEN
https://austingroupbugs.net/view.php?id=739
Nick completed his action to liaise with the C committee on this
issue. C23 is about to go to ballot, so the way to raise the issue
would be as a ballot comment. This could be done either as a UK or
US national body comment.
Andrew confirmed with the UK C Panel that we can submit comments.
Bug 728: Restrictions on signal handlers are both excessive and insufficient
OPEN
https://austingroupbugs.net/view.php?id=728
The alignment with C17 changes the requirements in this area. There
is still no allowance for accessing const objects or string literals,
so that is something we could consider adding as an extension to
C. Or we could raise the issue with the C committee if we want to
stay in sync with the C standard. Suggestion: raise it as a C23
ballot comment. Depending on the answer, we could implement what
they plan to do, or diverge (or leave things as they are).
AI Nick and Geoff: File ballot comments on C23 (through the US and/or UK
national bodies to WG14).
Bug 708: Make mblen, mbtowc, and wctomb thread-safe for alignment with C11 OPEN
https://austingroupbugs.net/view.php?id=708
This was discussed with WG14:
https://www.open-std.org/jtc1/sc22/wg14/www/docs/n2148.htm#dr_498
Here is the current wording in C23:
<blockquote>
The behavior of the multibyte character functions is affected by the
LC_CTYPE category of the current
locale. For a state-dependent encoding, each of the mbtowc and wctomb
functions is placed into its
initial conversion state prior to the first call to the function and can be
returned to that state by a
call for which its character pointer argument, s, is a null pointer.
Subsequent calls with s as other
than a null pointer cause the internal conversion state of the function to
be altered as necessary. It is
implementation-defined whether internal conversion state has thread storage
duration, and whether
a newly created thread has the same state as the current thread at the time
of creation, or the initial
conversion state. A call with s as a null pointer causes these functions to
return a nonzero value if
encodings have state dependency, and zero otherwise.
Changing the LC_CTYPE category causes the internal object describing the
conversion state of the
mbtowc and wctomb functions to have an indeterminate representation.
</blockquote>
DR 498 (URL above) seems to have an agreed wording change from April
2017, but it has not been applied.
AI: Nick to ask the WG14 convenor what happened to that DR.
Nick had completed his action. It appears the item was discussed but in the end
the C committee could not agree an acceptable change, and no alternate proposal
was available. We will need to accept the C wording for now.
Bug 700: Clarify strtoul's behaviour on strings representing negative numbers
OPEN
https://austingroupbugs.net/view.php?id=700
AI: Nick and Geoff to work together on a C23 ballot comment (against N3047
7.24.1.7 para 5).
Bug 689: Possibly unintended allowance for stdio deadlock OPEN
https://austingroupbugs.net/view.php?id=689
Change needs to be coordinated with C23.
AI: Nick and Geoff to work together on a C23 ballot comment (against N3047
7.23.3 para 3).
Bug 633: SIGEV_THREAD delivery renders many signal interfaces unsafe Accepted
as Marked
https://austingroupbugs.net/view.php?id=633
This item is tagged for TC3-2008.
On 2018 edition page 490 line 16984 section 2.4.2, change:
The signal mask of this thread is implementation-defined.
to:
It is implementation-defined whether the signal mask of this
thread has all signals except SIGKILL and SIGSTOP blocked, or
is the same as the mask that was in effect for the thread which
installed the sigevent notification handler at the time of the
call that installed the handler.
Bug 621: Ambiguos requirements for trap on EXIT Accepted as Marked
https://austingroupbugs.net/view.php?id=621
This item is tagged for TC3-2008.
After 2018 edition page 2420 line 77499 section 2.14 trap, add a new paragraph:
The EXIT condition shall occur when the shell terminates normally
(exits), and may occur when the shell terminates abnormally as
a result of delivery of a signal (other than SIGKILL) whose
trap action is the default.
Bug 618: require isatty and friends to set errno on failure OPEN
https://austingroupbugs.net/view.php?id=618
Action item to EricB: email to various lists to collect results for
sample program (see bug 503 comment 1005 for starting point) for
current errno behavior on various OS
Bug 614: Behavior of close() as a cancellation point is unspecified Accepted as
Marked
https://austingroupbugs.net/view.php?id=614
This item is tagged for Issue 8
On D2.1 page 483 line 16985 section 2.4.3 add posix_close() to the list of
async-signal-safe functions.
On D2.1 page 506 line 17923 section 2.9.5.2 add posix_close() to the "shall"
cancellation point list.
Bug 613: Relationship of automatic object lifetimes to cancellation cleanup
functions is not specified OPEN
https://austingroupbugs.net/view.php?id=613
We worked on this item and will complete it next time.
Next Steps
----------
The next calls are on:
Thu 2022-08-25 (general bugs)
No call Mon 2022-08-29
Thu 2022-09-01 (general bugs)
No call Mon 2022-09-05
Apologies in advance:
2022-08-25 Andrew Josey
2022-08-25 Tom Thompson
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: a.jo...@opengroup.org
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
