From: "Dmitry V. Levin" <ldv@strace.io>
To: Marco Cavenati <Marco.Cavenati@eurecom.fr>
Cc: Alejandro Colomar <alx@kernel.org>, linux-man@vger.kernel.org
Subject: Re: [PATCH] man/man2/ptrace.2: Add PTRACE_SET_SYSCALL_INFO, update struct ptrace_syscall_info
Date: Wed, 21 Jan 2026 18:56:39 +0200 [thread overview]
Message-ID: <20260121165639.GB6261@strace.io> (raw)
In-Reply-To: <20260121155550.281916-1-Marco.Cavenati@eurecom.fr>
On Wed, Jan 21, 2026 at 04:55:41PM +0100, Marco Cavenati wrote:
> Add documentation for the new ptrace request PTRACE_SET_SYSCALL_INFO,
> introduced in Linux 6.16.
>
> Add 'reserved' and 'flags' fields of struct ptrace_syscall_info.
>
> This description is based on kernel commit 26bb32768fe6552de044f782a58b3272073fbfc0
> ("ptrace: introduce PTRACE_SET_SYSCALL_INFO request") by Dmitry V. Levin.
>
> Signed-off-by: Marco Cavenati <Marco.Cavenati@eurecom.fr>
> ---
> AUTHORS | 1 +
> man/man2/ptrace.2 | 21 +++++++++++++++++++++
> 2 files changed, 22 insertions(+)
>
> diff --git a/AUTHORS b/AUTHORS
> index 9035d405a..f332932e1 100644
> --- a/AUTHORS
> +++ b/AUTHORS
> @@ -497,6 +497,7 @@ Marc-André Lureau <marcandre.lureau@redhat.com>
> Marcela Maslanova <mmaslano@redhat.com>
> Marcin Ślusarz <marcin.slusarz@gmail.com>
> Marco Bonelli <marco@mebeim.net>
> +Marco Cavenati <marco.cavenati@eurecom.fr>
> Marcus Folkesson <marcus.folkesson@gmail.com>
> Marcus Gelderie <redmnic@gmail.com>
> Marcus Huewe <suse-tux@gmx.de>
> diff --git a/man/man2/ptrace.2 b/man/man2/ptrace.2
> index 2da43dcb9..45d4c4c84 100644
> --- a/man/man2/ptrace.2
> +++ b/man/man2/ptrace.2
> @@ -1042,6 +1042,8 @@ structure contains the following fields:
> .EX
> struct ptrace_syscall_info {
> __u8 op; /* Type of system call stop */
> + __u8 reserved; /* Reserved for future use, must be zero */
> + __u16 flags; /* Reserved for future use, must be zero */
> __u32 arch; /* AUDIT_ARCH_* value; see seccomp(2) */
> __u64 instruction_pointer; /* CPU instruction pointer */
> __u64 stack_pointer; /* CPU stack pointer */
> @@ -1121,6 +1123,25 @@ is limited to type
> unless
> .B PTRACE_O_TRACESYSGOOD
> option is set before the corresponding system call stop has occurred.
> +.TP
> +.BR PTRACE_SET_SYSCALL_INFO " (since Linux 6.16)"
> +.\" commit 26bb32768fe6552de044f782a58b3272073fbfc0
> +Modify information about the system call that caused the stop.
> +The
> +.I data
> +argument is a pointer to
> +.I struct ptrace_syscall_info
> +that specifies the system call information to be set.
> +The
> +.I addr
> +argument should be set to
> +.IR "sizeof(struct ptrace_syscall_info)" .
> +Only the
> +.IR nr ,
> +.IR args ,
> +and
> +.I rval
> +fields can be modified.
> .\"
> .SS Death under ptrace
> When a (possibly multithreaded) process receives a killing signal
Looks good, thanks!
--
ldv
next prev parent reply other threads:[~2026-01-21 16:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 15:55 [PATCH] man/man2/ptrace.2: Add PTRACE_SET_SYSCALL_INFO, update struct ptrace_syscall_info Marco Cavenati
2026-01-21 16:56 ` Dmitry V. Levin [this message]
2026-02-10 20:14 ` Alejandro Colomar
2026-02-10 20:53 ` Dmitry V. Levin
2026-02-10 21:20 ` Alejandro Colomar
2026-02-10 21:41 ` Dmitry V. Levin
2026-02-10 21:52 ` Alejandro Colomar
2026-02-07 11:59 ` Marco Cavenati
2026-02-07 18:24 ` Alejandro Colomar
2026-02-07 18:38 ` Marco Cavenati
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=20260121165639.GB6261@strace.io \
--to=ldv@strace.io \
--cc=Marco.Cavenati@eurecom.fr \
--cc=alx@kernel.org \
--cc=linux-man@vger.kernel.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