From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: Richard Palethorpe <rpalethorpe@suse.com>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>, linux-man@vger.kernel.org
Subject: Re: [PATCH] wait.2: Add ESRCH for when pid == INT_MIN
Date: Sat, 10 Jul 2021 20:15:56 +0200 [thread overview]
Message-ID: <4bc36021-8d93-6af6-07ec-c388fcd2e4d1@gmail.com> (raw)
In-Reply-To: <20210708100853.17391-1-rpalethorpe@suse.com>
Hello Richard,
On 7/8/21 12:08 PM, Richard Palethorpe wrote:
> Please see upstream commit:
>
> commit dd83c161fbcc5d8be637ab159c0de015cbff5ba4
> Author: zhongjiang <zhongjiang@huawei.com>
> Date: Mon Jul 10 15:53:01 2017 -0700
>
> kernel/exit.c: avoid undefined behaviour when calling wait4()
>
> It avoids negating INT_MIN by returning early with ESRCH.
>
> Signed-off-by: Richard Palethorpe <rpalethorpe@suse.com>
Patch applied.
Thanks,
Alex
> ---
> man2/wait.2 | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/man2/wait.2 b/man2/wait.2
> index 5ae955b3f..63d872ee6 100644
> --- a/man2/wait.2
> +++ b/man2/wait.2
> @@ -455,6 +455,15 @@ was caught; see
> The
> .I options
> argument was invalid.
> +.TP
> +.B ESRCH
> +(for
> +.BR wait ()
> +or
> +.BR waitpid ())
> +.I pid
> +is equal to
> +.I INT_MIN
> .SH CONFORMING TO
> SVr4, 4.3BSD, POSIX.1-2001.
> .SH NOTES
>
--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
next prev parent reply other threads:[~2021-07-10 18:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 10:08 [PATCH] wait.2: Add ESRCH for when pid == INT_MIN Richard Palethorpe
2021-07-10 18:15 ` Alejandro Colomar (man-pages) [this message]
2021-07-12 16:11 ` Jakub Wilk
2021-07-13 7:37 ` Richard Palethorpe
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=4bc36021-8d93-6af6-07ec-c388fcd2e4d1@gmail.com \
--to=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=rpalethorpe@suse.com \
/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 NNTP newsgroup(s).