public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Dmitry V. Levin" <ldv@strace.io>
To: Alex Colomar <alx.manpages@gmail.com>
Cc: "Φώτης Βαλασιάδης" <fvalasiad@gmail.com>,
	linux-man@vger.kernel.org, mtk.manpages@gmail.com,
	"Nate Eldredge" <nate@thatsmathematics.com>,
	"Elvira Khabirova" <lineprinter0@gmail.com>
Subject: Re: [PATCH] ptrace.2: Add details about usage of PTRACE_GET_SYSCALL_INFO
Date: Sat, 25 Feb 2023 12:39:44 +0300	[thread overview]
Message-ID: <20230225093944.GA16562@altlinux.org> (raw)
In-Reply-To: <fece7cb1-a4d7-d19f-16af-d82c95f558be@gmail.com>

Hi Alex,

On Sat, Feb 25, 2023 at 02:21:51AM +0100, Alex Colomar wrote:
> Hi Dmitry!
> 
> On 2/25/23 01:08, Dmitry V. Levin wrote:
> > On Sat, Feb 25, 2023 at 01:43:18AM +0200, Φώτης Βαλασιάδης wrote:
> >> Better?
> >>
> >> diff --git a/man2/ptrace.2 b/man2/ptrace.2
> >> index 55d9fd36d..ad0543b0b 100644
> >> --- a/man2/ptrace.2
> >> +++ b/man2/ptrace.2
> >> @@ -1111,6 +1111,15 @@ stop.
> >>    .B PTRACE_SYSCALL_INFO_NONE
> >>    No component of the union contains relevant information.
> >>    .RE
> >> +.IP
> >> +Note that in case of
> >> +syscall entry or exit stops, the data returned by
> >> +.B PTRACE_GET_SYSCALL_INFO
> >> +is limited to type
> >> +.B PTRACE_SYSCALL_INFO_NONE
> >> +unless
> >> +.B PTRACE_O_TRACESYSGOOD
> >> +option is set before the corresponding ptrace stop has occurred.
> >>    .\"
> >>    .SS Death under ptrace
> >>    When a (possibly multithreaded) process receives a killing signal
> > 
> > LGTM, thanks.
> 
> Ahh, I see you already CCd Nate.  Thanks!
> 
> Thanks for the review!  I should take that as an Acked-by?

Sure, feel free to add:

Reviewed-by: Dmitry V. Levin <ldv@strace.io>


-- 
ldv

  reply	other threads:[~2023-02-25  9:39 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-24 16:31 [PATCH] ptrace.2: Add details about usage of PTRACE_GET_SYSCALL_INFO Fotios Valasiadis
2023-02-24 18:53 ` Dmitry V. Levin
2023-02-24 19:11   ` Φώτης Βαλασιάδης
2023-02-24 22:05     ` Dmitry V. Levin
2023-02-24 23:05       ` Φώτης Βαλασιάδης
2023-02-24 23:31         ` Dmitry V. Levin
2023-02-24 23:43           ` Φώτης Βαλασιάδης
2023-02-25  0:08             ` Dmitry V. Levin
2023-02-25  1:21               ` Alex Colomar
2023-02-25  9:39                 ` Dmitry V. Levin [this message]
2023-02-25  1:18 ` Alex Colomar
2023-02-25  1:36   ` Φώτης Βαλασιάδης
2023-02-25  2:07   ` Nate Eldredge
  -- strict thread matches above, loose matches on Subject: below --
2023-02-25  2:42 Fotios Valasiadis
2023-02-25 10:10 ` Dmitry V . Levin
2023-02-25 10:33   ` Φώτης Βαλασιάδης
2023-02-25 10:42     ` Dmitry V . Levin
2023-02-25 10:56 Fotios Valasiadis
2023-02-26 21:58 ` Alejandro Colomar
2023-02-26 22:03   ` Dmitry V . Levin
2023-02-26 22:05     ` Alejandro Colomar
2023-02-26 22:14       ` Φώτης Βαλασιάδης
2023-02-26 22:42         ` Alejandro Colomar
2023-02-26 23:30           ` Φώτης Βαλασιάδης
2023-02-26 23:22 ` Fotios Valasiadis
2023-02-27  0:19   ` Alejandro Colomar
2023-02-27  0:41     ` Φώτης Βαλασιάδης
2023-02-27 13:28       ` Alejandro Colomar
2023-02-27 15:33         ` Dmitry V. Levin
2023-02-27 15:35           ` Alejandro Colomar
     [not found]             ` <b57591a9-5ba1-5192-f376-f2de812a9086@gmail.com>
2023-02-27 18:48               ` Alejandro Colomar
2023-02-27 19:17                 ` Fotios Valasiadis
2023-02-27 19:19                   ` Φώτης Βαλασιάδης
2023-03-01 19:28                     ` Φώτης Βαλασιάδης
2023-03-01 21:00                   ` Alejandro Colomar

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=20230225093944.GA16562@altlinux.org \
    --to=ldv@strace.io \
    --cc=alx.manpages@gmail.com \
    --cc=fvalasiad@gmail.com \
    --cc=lineprinter0@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=nate@thatsmathematics.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