From: Oleg Nesterov <oleg@redhat.com>
To: Renzo Davoli <renzo@cs.unibo.it>
Cc: linux-kernel@vger.kernel.org,
"Michal Suchánek" <msuchanek@suse.de>,
"Kees Cook" <kees@kernel.org>,
"Andy Lutomirski" <luto@amacapital.net>,
"Will Drewry" <wad@chromium.org>,
"Thomas Gleixner" <tglx@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Shuah Khan" <shuah@kernel.org>,
"Dmitry V . Levin" <ldv@strace.io>,
"Alexey Gladkov" <legion@kernel.org>,
"Eugene Syromyatnikov" <evgsyr@gmail.com>,
"Davide Berardi" <berardi.dav@gmail.com>,
"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
"Heiko Carstens" <hca@linux.ibm.com>,
"Vasily Gorbik" <gor@linux.ibm.com>,
"Madhavan Srinivasan" <maddy@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org,
linux-kselftest@vger.kernel.org, strace-devel@lists.strace.io
Subject: Re: [PATCH v11 2/3] ptrace: add PTRACE_SET_SYSCALL_INFO syscall skipping support
Date: Tue, 17 Nov 2026 17:23:19 +0100 [thread overview]
Message-ID: <avx_d9SSnpwhSyqU@redhat.com> (raw)
In-Reply-To: <20261114181923.370930-3-renzo@cs.unibo.it>
On 11/14, Renzo Davoli wrote:
>
> Extend PTRACE_SET_SYSCALL_INFO to support skipping a system call
> triggered via seccomp.
...
> Signed-off-by: Renzo Davoli <renzo@cs.unibo.it>
> [v8: skip via seccomp_ptrace_skip_syscall() instead of syscall_set_nr(-1),
> separate ptrace_set_syscall_info_seccomp_skip(), reject later
> PTRACE_SYSCALL_INFO_SECCOMP updates during the same stop]
> [v11: report the stop as PTRACE_SYSCALL_INFO_EXIT once the syscall is
> skipped, instead of rejecting PTRACE_SYSCALL_INFO_SECCOMP explicitly]
> Assisted-by: claude-opus-5-5
> ---
> kernel/ptrace.c | 49 +++++++++++++++++++++++++++++++++++++++++++++++--
> 1 file changed, 47 insertions(+), 2 deletions(-)
Reviewed-by: Oleg Nesterov <oleg@redhat.com>
Sashiko has some concerns
https://sashiko.dev/#/patchset/20261114181923.370930-1-renzo%40cs.unibo.it
but IIUC this is the "pre-existing" problem fixed by
[PATCH v3 0/2] powerpc/syscall: Fix the return value of skipped syscalls
https://lore.kernel.org/lkml/20261030084926.1068384-1-renzo@cs.unibo.it/
so this change do not need to depend on the powerpc-specific fix above.
Right? Just to be sure...
Oleg.
next prev parent reply other threads:[~2026-11-17 16:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-14 18:19 [PATCH v11 0/3] PTRACE_SET_SYSCALL_INFO: add support for seccomp syscall skipping Renzo Davoli
2026-11-14 18:19 ` [PATCH v11 1/3] seccomp: let the tracer skip a syscall independently of its number Renzo Davoli
2026-11-14 18:40 ` sashiko-bot
2026-11-17 16:54 ` Oleg Nesterov
2026-11-14 18:19 ` [PATCH v11 2/3] ptrace: add PTRACE_SET_SYSCALL_INFO syscall skipping support Renzo Davoli
2026-11-14 18:44 ` sashiko-bot
2026-11-17 16:23 ` Oleg Nesterov [this message]
2026-11-14 18:19 ` [PATCH v11 3/3] selftests/ptrace: add a test case for PTRACE_SET_SYSCALL_INFO syscall skipping Renzo Davoli
2026-11-14 18:27 ` sashiko-bot
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=avx_d9SSnpwhSyqU@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=berardi.dav@gmail.com \
--cc=evgsyr@gmail.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=kees@kernel.org \
--cc=ldv@strace.io \
--cc=legion@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=luto@amacapital.net \
--cc=maddy@linux.ibm.com \
--cc=msuchanek@suse.de \
--cc=renzo@cs.unibo.it \
--cc=shuah@kernel.org \
--cc=strace-devel@lists.strace.io \
--cc=tglx@kernel.org \
--cc=tsbogend@alpha.franken.de \
--cc=wad@chromium.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 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.