From: Oleg Nesterov <oleg@redhat.com>
To: Renzo Davoli <renzo@cs.unibo.it>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Shuah Khan <shuah@kernel.org>, Alexey Gladkov <legion@kernel.org>,
Eugene Syromyatnikov <evgsyr@gmail.com>,
Davide Berardi <berardi.dav@gmail.com>,
strace-devel@lists.strace.io, "Dmitry V . Levin" <ldv@strace.io>
Subject: Re: [PATCH v2 4/5] ptrace: add PTRACE_SYSCALL_INFO_FLAG_SET_IP
Date: Fri, 3 Jul 2026 17:54:18 +0200 [thread overview]
Message-ID: <akfbKiJqXETm5mY7@redhat.com> (raw)
In-Reply-To: <akfO2xqhDjWU-uDs@cs.unibo.it>
On 07/03, Renzo Davoli wrote:
>
> On Fri, Jul 03, 2026 at 01:04:59PM +0200, Oleg Nesterov wrote:
> > On 07/03, Renzo Davoli wrote:
> > >
> > > This flag adds support for modifying the tracee's instruction pointer.
> > >
> > > To do this, the tracer stores the new instruction pointer value in the
> > > instruction_pointer field of the ptrace_syscall_info structure and
> > > sets the PTRACE_SYSCALL_INFO_FLAG_SET_IP flag in the flags field.
> >
> > But why? Who will use this feature and for what? How often?
> >
> > I think the changelog should be more convincing...
>
> I'll add this to V3 cover letter.
[... snip ...]
OK, but I'd suggest to add this to the changelog of the patch which adds
PTRACE_SYSCALL_INFO_FLAG_SET_IP
And in fact, I'd I also suggest to send 3-5 as a separate series...
Oleg.
next prev parent reply other threads:[~2026-07-03 15:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 10:50 [PATCH v2 0/5] ptrace_set_syscall_info: add support for seccomp syscall skipping and instruction pointer modification Renzo Davoli
2026-07-03 10:50 ` [PATCH v2 1/5] ptrace: PTRACE_SET_SYSCALL_INFO syscall skipping support Renzo Davoli
2026-07-03 10:58 ` Oleg Nesterov
2026-07-03 11:48 ` Oleg Nesterov
2026-07-03 10:50 ` [PATCH v2 2/5] selftests/ptrace: add a test case for PTRACE_SYSCALL_INFO syscall skipping Renzo Davoli
2026-07-03 10:50 ` [PATCH v2 3/5] asm/ptrace.h: add instruction_pointer_set Renzo Davoli
2026-07-03 10:50 ` [PATCH v2 4/5] ptrace: add PTRACE_SYSCALL_INFO_FLAG_SET_IP Renzo Davoli
2026-07-03 11:04 ` Oleg Nesterov
2026-07-03 15:01 ` Renzo Davoli
2026-07-03 15:54 ` Oleg Nesterov [this message]
2026-07-04 9:11 ` Renzo Davoli
2026-07-03 10:50 ` [PATCH v2 5/5] selftests/ptrace: add a test case for PTRACE_SYSCALL_INFO_FLAG_SET_IP Renzo Davoli
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=akfbKiJqXETm5mY7@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=berardi.dav@gmail.com \
--cc=evgsyr@gmail.com \
--cc=ldv@strace.io \
--cc=legion@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=renzo@cs.unibo.it \
--cc=shuah@kernel.org \
--cc=strace-devel@lists.strace.io \
/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.