The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Renzo Davoli <renzo@cs.unibo.it>, "Dmitry V . Levin" <ldv@strace.io>
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>,
	Mike Frysinger <vapier@gentoo.org>,
	Davide Berardi <berardi.dav@gmail.com>,
	strace-devel@lists.strace.io
Subject: Re: [PATCH v3 1/2] ptrace: PTRACE_SET_SYSCALL_INFO syscall skipping support
Date: Tue, 7 Jul 2026 18:35:51 +0200	[thread overview]
Message-ID: <ak0q59BhB7DHVfaM@redhat.com> (raw)
In-Reply-To: <20260707112107.920752-2-renzo@cs.unibo.it>

On 07/07, Renzo Davoli wrote:
>
> +	child_op = ptrace_get_syscall_info_op(child);
> +	if (child_op != info.op) {
> +		if (info.op == PTRACE_SYSCALL_INFO_EXIT &&
> +				 child_op == PTRACE_SYSCALL_INFO_SECCOMP)
> +			skip_syscall = true;
> +		else
> +			return -EINVAL;

OK, I have to agree, we can't allow _ENTRY -> _EXIT transition right now.

Signed-off-by: Oleg Nesterov <oleg@redhat.com>

---------------------------------------------------------------------------
Hopefully we can allow _ENTRY -> _EXIT later, when/if we have some help from
arch/ maintainers.

Although I think that the much more likely case is when Dmitry who understands
_every_ arch/ will have time/motivation to make the neccessary changes ;) Hmm...
but you removed him from CC list, please don't do this. Add him back.

And... As I said, I agree with any naming. But somehow I don't like "child_op".
Again, I won't argue, but if you will have any reason to send V4, please think
about something else. "reported_op" or just "op". To me "child_op" looks a bit
confusing, but this is minor/subjective, feel free to ignore.

Oleg.


  reply	other threads:[~2026-07-07 16:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-07 11:21 [PATCH v3 0/2] ptrace_set_syscall_info: add support for seccomp syscall skipping Renzo Davoli
2026-07-07 11:21 ` [PATCH v3 1/2] ptrace: PTRACE_SET_SYSCALL_INFO syscall skipping support Renzo Davoli
2026-07-07 16:35   ` Oleg Nesterov [this message]
2026-07-07 17:19   ` Dmitry V. Levin
2026-07-07 17:44     ` Oleg Nesterov
2026-07-07 11:21 ` [PATCH v3 2/2] selftests/ptrace: add a test case for PTRACE_SYSCALL_INFO syscall skipping Renzo Davoli
2026-07-08  7:47   ` Dmitry V. Levin

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=ak0q59BhB7DHVfaM@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 \
    --cc=vapier@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox