From: Alistair Francis <alistair23@gmail.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH 5/7] linux: Use waitid on wait4 if __NR_wait4 is not defined
Date: Tue, 3 Dec 2019 10:58:47 -0800 [thread overview]
Message-ID: <CAKmqyKMCjZD7rAX+FJoKq894sBhf7pjmfCh+j=GmOs_bWK1WDg@mail.gmail.com> (raw)
In-Reply-To: <d5c03878-404a-888a-a9df-a491858b5de4@linaro.org>
On Mon, Nov 25, 2019 at 4:42 AM Adhemerval Zanella
<adhemerval.zanella@linaro.org> wrote:
>
>
>
> On 25/11/2019 09:39, Adhemerval Zanella wrote:
>
> > So it seems that __ASSUME_WAITID_PID0_P_PGID should be a safe call to
> > avoid such theoretical scenarios. I will rework how the flag is used
> > to mimic other assume usage where newer kernel version undef the flag,
> > so it should be simpler to remove it once the minimum kernel is lifted.
> >
>
> In fact I think change the __ASSUME_WAITID_PID0_P_PGID won't be much
> a improvement
Any update on this series?
Alistair
next prev parent reply other threads:[~2019-12-03 19:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 14:46 [PATCH 1/7] Remove __waitpid_nocancel Adhemerval Zanella
2019-11-14 14:46 ` [PATCH 2/7] nptl: Move wait implementation to libc Adhemerval Zanella
2019-11-14 14:47 ` [PATCH 3/7] nptl: Move waitpid " Adhemerval Zanella
2019-11-14 14:47 ` [PATCH 4/7] Implement wait in terms of waitpid Adhemerval Zanella
2019-11-14 14:47 ` [PATCH 5/7] linux: Use waitid on wait4 if __NR_wait4 is not defined Adhemerval Zanella
2019-11-15 18:27 ` Alistair Francis
2019-11-21 17:48 ` Adhemerval Zanella
2019-11-21 17:52 ` Adhemerval Zanella
2019-11-21 18:41 ` Alistair Francis
2019-11-22 12:15 ` Adhemerval Zanella
2019-11-22 20:00 ` Alistair Francis
2019-11-25 12:39 ` Adhemerval Zanella
2019-11-25 12:42 ` Adhemerval Zanella
2019-12-03 18:58 ` Alistair Francis [this message]
2019-12-03 19:18 ` Adhemerval Zanella
2019-11-14 14:47 ` [PATCH 6/7] Implement waitpid in terms of wait4 Adhemerval Zanella
2019-11-14 14:47 ` [PATCH 7/7] Consolidate wait3 implementations Adhemerval Zanella
2019-11-14 15:44 ` Alistair Francis
2019-12-19 15:33 ` 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='CAKmqyKMCjZD7rAX+FJoKq894sBhf7pjmfCh+j=GmOs_bWK1WDg@mail.gmail.com' \
--to=alistair23@gmail.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).