From: Christian Brauner <christian.brauner@ubuntu.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH 3/3] posix: Remove posix waitid
Date: Wed, 20 Nov 2019 16:14:12 +0100 [thread overview]
Message-ID: <20191120151410.z57vmxgcx3q2njna@wittgenstein> (raw)
In-Reply-To: <20191120141535.5303-3-adhemerval.zanella@linaro.org>
On Wed, Nov 20, 2019 at 11:15:35AM -0300, Adhemerval Zanella wrote:
> The POSIX waitid implementation is problematic in some ways:
>
> - It emulates using waitpid, which default implementation calls
> wait4 and wait4 returns ENOSYS as default.
>
> - Also by using waitpid it does not allod support the WNOWAIT,
> WEXITED, WSTOPPED, or WCONTINUED flag. With current POSIX
> specification the flags are no longer marked as optional.
>
> Also due BZ#23091 Hurd still uses the implementation, so it is moved
> to as a Hurd arch-specific folder (with some minor cleanups).
>
> Checked against a i686-gnu (run-built-tests=no)
I haven't followed that thread too closely, so sorry for maybe redundant
questions.
Does this mean you're removing support for the waitid() _syscall_ from
glibc? How do you intend to deal with P_PIDFD released with kernel 5.3?
Christian
next prev parent reply other threads:[~2019-11-20 15:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 14:15 [PATCH 1/3] support: Add support_process_state_wait Adhemerval Zanella
2019-11-20 14:15 ` [PATCH 2/3] posix: Refactor tst-waitid Adhemerval Zanella
2019-11-20 17:33 ` Joseph Myers
2019-11-20 19:42 ` Adhemerval Zanella
2019-12-20 12:36 ` Adhemerval Zanella
2019-11-20 14:15 ` [PATCH 3/3] posix: Remove posix waitid Adhemerval Zanella
2019-11-20 15:14 ` Christian Brauner [this message]
2019-11-20 17:14 ` Adhemerval Zanella
2019-12-20 12:36 ` Adhemerval Zanella
2019-12-20 12:35 ` [PATCH 1/3] support: Add support_process_state_wait Adhemerval Zanella
2019-12-20 14:09 ` Florian Weimer
2019-12-20 20:19 ` Adhemerval Zanella
2019-12-20 20:32 ` Florian Weimer
2019-12-26 14:20 ` Adhemerval Zanella
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191120151410.z57vmxgcx3q2njna@wittgenstein \
--to=christian.brauner@ubuntu.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).