From: Oleg Nesterov <oleg@redhat.com>
To: Renzo Davoli <renzo@cs.unibo.it>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
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>,
"open list:MIPS" <linux-mips@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] ptrace: PTRACE_SET_SYSCALL_INFO syscall skipping support
Date: Tue, 7 Jul 2026 18:04:56 +0200 [thread overview]
Message-ID: <ak0jqCyrtFg7azDM@redhat.com> (raw)
In-Reply-To: <ak0MykKEi4b6AHRV@cs.unibo.it>
On 07/07, Renzo Davoli wrote:
>
> On Sun, Jul 05, 2026 at 04:38:05PM +0200, Oleg Nesterov wrote:
> > OK, lets only allow the _SECCOMP -> _EXIT transition for now.
> done in v3.
> > But will it work on MIPS?
>
> IMHO yes, it will (would).
Agreed, it is not that I think it won't... but it would be nice to have an ACK
from arch/mips maintainers. syscall_trace_enter() is called from MIPS asm code
which I obviously can't understand.
Nevermind. Let me ack your V3.
Oleg.
next prev parent reply other threads:[~2026-07-07 16:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-04 14:26 [PATCH v2 0/2] ptrace_set_syscall_info: add support for seccomp syscall skipping Renzo Davoli
2026-07-04 14:26 ` [PATCH v2 1/2] ptrace: PTRACE_SET_SYSCALL_INFO syscall skipping support Renzo Davoli
2026-07-05 6:41 ` Renzo Davoli
2026-07-05 14:38 ` Oleg Nesterov
2026-07-07 14:27 ` Renzo Davoli
2026-07-07 16:04 ` Oleg Nesterov [this message]
2026-07-07 16:09 ` Thomas Bogendoerfer
2026-07-10 12:34 ` Thomas Bogendoerfer
2026-07-12 21:27 ` Oleg Nesterov
2026-07-06 16:03 ` Dmitry V. Levin
2026-07-04 14:26 ` [PATCH v2 2/2] selftests/ptrace: add a test case for PTRACE_SYSCALL_INFO syscall skipping 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=ak0jqCyrtFg7azDM@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=linux-mips@vger.kernel.org \
--cc=renzo@cs.unibo.it \
--cc=shuah@kernel.org \
--cc=strace-devel@lists.strace.io \
--cc=tsbogend@alpha.franken.de \
/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.