From: "Dmitry V. Levin" <ldv@altlinux.org>
To: Michael Kerrisk <mtk.manpages@gmail.com>
Cc: Elvira Khabirova <lineprinter@altlinux.org>, linux-man@vger.kernel.org
Subject: [PATCH] ptrace.2: document PTRACE_GET_SYSCALL_INFO
Date: Mon, 2 Sep 2019 15:38:58 +0300 [thread overview]
Message-ID: <20190902123858.GA8956@altlinux.org> (raw)
PTRACE_GET_SYSCALL_INFO request was introduced by Linux kernel commit
201766a20e30f982ccfe36bebfad9602c3ff574a aka v5.3-rc1~65^2~23.
Signed-off-by: Dmitry V. Levin <ldv@altlinux.org>
---
man2/ptrace.2 | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/man2/ptrace.2 b/man2/ptrace.2
index 8b8daf238..3b774f87b 100644
--- a/man2/ptrace.2
+++ b/man2/ptrace.2
@@ -1005,6 +1005,27 @@ of the
.IR "struct user_desc"
is ignored; in other words,
this ptrace operation can't be used to allocate a free TLS entry.)
+.TP
+.BR PTRACE_GET_SYSCALL_INFO " (since Linux 5.3)"
+.\" commit 201766a20e30f982ccfe36bebfad9602c3ff574a
+Retrieve information about the syscall that caused the stop.
+The information is placed into the buffer pointed by
+.I data
+argument, which should be a pointer to a buffer of type
+.IR "struct ptrace_syscall_info" .
+The
+.I addr
+argument contains the size of the buffer pointed to
+by
+.I data
+argument (i.e.,
+.IR "sizeof(struct ptrace_syscall_info)" ).
+The return value contains the number of bytes available
+to be written by the kernel.
+If the size of data to be written by the kernel exceeds the size
+specified by
+.I addr
+argument, the output is truncated.
.\"
.SS Death under ptrace
When a (possibly multithreaded) process receives a killing signal
--
ldv
next reply other threads:[~2019-09-02 12:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 12:38 Dmitry V. Levin [this message]
2019-09-10 10:51 ` [PATCH] ptrace.2: document PTRACE_GET_SYSCALL_INFO Michael Kerrisk (man-pages)
2019-09-11 17:38 ` [PATCH] ptrace.2: document struct ptrace_syscall_info Dmitry V. Levin
2019-09-12 9:17 ` Michael Kerrisk (man-pages)
2019-09-13 15:40 ` Dmitry V. Levin
2019-09-13 18:48 ` Michael Kerrisk (man-pages)
2019-09-13 19:37 ` Dmitry V. Levin
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=20190902123858.GA8956@altlinux.org \
--to=ldv@altlinux.org \
--cc=lineprinter@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.