public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Collin Funk <collin.funk1@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: libc-alpha@sourceware.org,  linux-man@vger.kernel.org
Subject: Re: fork(2), _Fork(), POSIX.1-2024, and AS-safety
Date: Sat, 17 May 2025 11:11:38 -0700	[thread overview]
Message-ID: <87ecwnf6p1.fsf@gmail.com> (raw)
In-Reply-To: <mp3cwzbgvqw2m53jykhfz5xloihxcr5v5bwynig3cxrsmmpqhe@eaok355sjksi>

Hi Alejandro,

Alejandro Colomar <alx@kernel.org> writes:

> While updating the manual pages for POSIX.1-2024, I've realized about
> the existence of _Fork().  The GNU documentation says it's a GNU
> extension.  I guess it needs to be updated now that it's standard.
>
> I'll need to write a new manual page page for it, and change the
> existing ones to note that fork(2) isn't AS-safe.

Thank you for the reminder. I did this earlier this year in commit
ee33752b5d8c53eb5a357f67ab7ab6288fba5fd9:

    manual: Document functions adopted by POSIX.1-2024.
    
    Here is a patch updating the documentation to mention GNU and BSD
    extensions that were adopted by POSIX.1-2024.
    
    * manual/llio.texi (Memory-mapped I/O): Add that MAP_ANON and
    MAP_ANONYMOUS were added by POSIX.1-2024.
    * manual/memory.texi (Changing Block Size): Mention that reallocarray
    was added by POSIX.1-2024.
    * manual/message.texi (Message Translation): Adjust wording to match
    standardization.
    (Translation with gettext): Mention the gettext family of functions were
    added by POSIX.1-2024.
    * manual/pattern.texi (Wildcard Matching): Mention that FNM_CASEFOLD was
    added by POSIX.1-2024.
    * manual/process.texi (Creating a Process): Mention that _Fork and
    WCOREDUMP were added by POSIX.1-2024.
    * manual/signal.texi (Miscellaneous Signals): Mention that SIGWINCH was
    added by POSIX-1.2024.
    * manual/startup.texi (Environment Access): Mention that secure_getenv
    was added by POSIX.1-2024.
    * manual/string.texi (Truncating Strings): Mention that strlcpy,
    strlcat, wcslcpy, and wslcat were added by POSIX-1.2024.
    (Search Functions): Document that memmem was added by POSIX-1.2024.
    * manual/terminal.texi (Allocation): Mention that ptsname_r was added by
    POSIX-1.2024.
    * manual/threads.texi (Waiting with Explicit Clocks): Move node under
    POSIX Threads.  Mention pthread_cond_clockwait,
    pthread_rwlock_clockrdlock, and pthread_rwlock_clockwrlock were added by
    POSIX-1.2024.
    (Joining Threads): New node under Non-POSIX Extensions.
    
    Reviewed-by: Adhemerval Zanella  <adhemerval.zanella@linaro.org>
    Signed-off-by: Collin Funk <collin.funk1@gmail.com>

And in commit 93623c03d527dcec76694ab0fcc197193922d1a8 updated getdelim
and getline which were added by POSIX.1-2008 based on the GNU extension:

    manual: Update standardization of getline and getdelim [BZ #32830]
    
    * manual/stdio.texi (Line Input): Document that getline and getdelim
    where GNU extensions until standardized in POSIX.1-2008.  Add restrict
    to function prototypes.
    
    Signed-off-by: Collin Funk <collin.funk1@gmail.com>
    Reviewed-by: Adhemerval Zanella  <adhemerval.zanella@linaro.org>

Next time I will remember to remind you on linux-man@vger.kernel.org. I
would offer to do the patch myself, but I don't know roff. :)

Collin

  reply	other threads:[~2025-05-17 18:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-17 10:49 fork(2), _Fork(), POSIX.1-2024, and AS-safety Alejandro Colomar
2025-05-17 18:11 ` Collin Funk [this message]
2025-05-17 19:16   ` Alejandro Colomar
2025-05-18  0:01     ` Learning man(7) (was: fork(2), _Fork(), POSIX.1-2024, and AS-safety) G. Branden Robinson
2025-05-23 16:22       ` Learning man(7) Zack Weinberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ecwnf6p1.fsf@gmail.com \
    --to=collin.funk1@gmail.com \
    --cc=alx@kernel.org \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-man@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox