linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: nforro@redhat.com
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: [PATCH] execve.2: clarify signal sent to the process on late failure
Date: Wed, 29 Apr 2020 21:51:14 +0200	[thread overview]
Message-ID: <64d7c699-1940-bd17-99fa-24d4d7aa18b2@gmail.com> (raw)
In-Reply-To: <c3c73e5e62c5981f3e21de0febe3d651bc95a6d8.camel@redhat.com>

Hello Nikola,

On 4/29/20 5:30 PM, Nikola Forró wrote:
> Signed-off-by: Nikola Forró <nforro@redhat.com>

Thanks. patch applied.

Cheers,

Michael

> ---
>  man2/execve.2 | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/man2/execve.2 b/man2/execve.2
> index ab5843840..109c0d57d 100644
> --- a/man2/execve.2
> +++ b/man2/execve.2
> @@ -640,7 +640,10 @@ failure may occur past the point of no return:
>  the original executable image has been torn down,
>  but the new image could not be completely built.
>  In such cases, the kernel kills the process with a
> -.BR SIGKILL
> +.\" commit 19d860a140beac48a1377f179e693abe86a9dac9
> +.BR SIGSEGV
> +.RB ( SIGKILL
> +until Linux 3.17)
>  signal.
>  .\"
>  .SS Interpreter scripts
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

      reply	other threads:[~2020-04-29 19:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-29 15:30 [PATCH] execve.2: clarify signal sent to the process on late failure Nikola Forró
2020-04-29 19:51 ` Michael Kerrisk (man-pages) [this message]

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=64d7c699-1940-bd17-99fa-24d4d7aa18b2@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=nforro@redhat.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).