From: Sven Schnelle <svens@linux.ibm.com>
To: strace development discussions <strace-devel@lists.strace.io>
Cc: linux-kernel@vger.kernel.org, Renzo Davoli <renzo@cs.unibo.it>,
Andrew Morton <akpm@linux-foundation.org>,
Oleg Nesterov <oleg@redhat.com>, Shuah Khan <shuah@kernel.org>,
Alexey Gladkov <legion@kernel.org>,
Eugene Syromyatnikov <evgsyr@gmail.com>,
Davide Berardi <berardi.dav@gmail.com>,
"Dmitry V . Levin" <ldv@strace.io>
Subject: Re: [PATCH v2 1/5] ptrace: PTRACE_SET_SYSCALL_INFO syscall skipping support
Date: Thu, 09 Jul 2026 09:04:34 +0200 [thread overview]
Message-ID: <yt9d33xswsn1.fsf@linux.ibm.com> (raw)
In-Reply-To: <20260703105027.539399-2-renzo@cs.unibo.it>
Renzo Davoli <renzo@cs.unibo.it> writes:
> This patch extends PTRACE_SET_SYSCALL_INFO with support for skipping a system
> call triggered via seccomp.
>
> When the tracer retrieves a ptrace_syscall_info structure with
> op == PTRACE_SYSCALL_INFO_SECCOMP, it may choose to skip the system
> call by changing op to PTRACE_SYSCALL_INFO_EXIT and
> populating the exit union fields (rval and is_error) to define
> the return value and error status for the tracee.
Is it possible to indicate the information whether the syscall should be
skipped via a dedicated return value? There's currently work going on[1]
to do this for seccomp, and it would be awkward if ptrace introduces
this at the same time.
At least for s390 this is problematic because it shares gprs[2] for both
syscall number and return value, and if I read the thread correctly this
also doesn't work for MIPS?
[1] https://patchew.org/linux/akVRcPsD._5FR._5FCE1qW@kunlun.suse.cz/
next prev parent reply other threads:[~2026-07-09 7:05 UTC|newest]
Thread overview: 16+ 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-09 7:04 ` Sven Schnelle [this message]
2026-07-09 7:59 ` Dmitry V. Levin
2026-07-09 13:47 ` Oleg Nesterov
2026-07-09 13:58 ` 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
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=yt9d33xswsn1.fsf@linux.ibm.com \
--to=svens@linux.ibm.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=oleg@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox