public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Dmitry V. Levin" <ldv@altlinux.org>
To: Michael Kerrisk <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: [PING v1] [PATCH] ptrace.2: mention PTRACE_GET_SYSCALL_INFO in RETURN VALUE section
Date: Mon, 26 Apr 2021 21:39:28 +0300	[thread overview]
Message-ID: <20210426183927.GA11060@altlinux.org> (raw)
In-Reply-To: <20210222164256.GA1943@altlinux.org>

Ping?

On Mon, Feb 22, 2021 at 07:42:57PM +0300, Dmitry V. Levin wrote:
> Mirror the wording about PTRACE_GET_SYSCALL_INFO return value semantics
> from "DESCRIPTION" section to "RETURN VALUE" section.
> 
> Reported-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
> Complements: fc91449cb "ptrace.2: Document PTRACE_GET_SYSCALL_INFO"
> Signed-off-by: Dmitry V. Levin <ldv@altlinux.org>
> ---
>  man2/ptrace.2 | 7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
> 
> diff --git a/man2/ptrace.2 b/man2/ptrace.2
> index 5245338ba..c5e75c274 100644
> --- a/man2/ptrace.2
> +++ b/man2/ptrace.2
> @@ -2327,8 +2327,11 @@ On success, the
>  requests return the requested data (but see NOTES),
>  the
>  .B PTRACE_SECCOMP_GET_FILTER
> -request returns the number of instructions in the BPF program, and
> -other requests return zero.
> +request returns the number of instructions in the BPF program,
> +the
> +.B PTRACE_GET_SYSCALL_INFO
> +request returns the number of bytes available to be written by the kernel,
> +and other requests return zero.
>  .PP
>  On error, all requests return \-1, and
>  .I errno
> -- 
> ldv

-- 
ldv

  reply	other threads:[~2021-04-26 18:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22 16:42 [PATCH] ptrace.2: mention PTRACE_GET_SYSCALL_INFO in RETURN VALUE section Dmitry V. Levin
2021-04-26 18:39 ` Dmitry V. Levin [this message]
2021-04-27  7:30   ` [PING v1] " Alejandro Colomar (man-pages)

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=20210426183927.GA11060@altlinux.org \
    --to=ldv@altlinux.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.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