Re: [PATCH v4 2/2] selftests/ptrace: check that PTRACE_SET_SYSCALL_INFO rejects invalid error values
From: Renzo Davoli
Date: Tue Nov 17 2026 - 04:51:58 EST
On Tue, Nov 17, 2026 at 10:05:37AM +0100, Renzo Davoli wrote:
> Thanks Andrew, the fixup is correct and a good addition: the test now
> covers both sides of the -MAX_ERRNO boundary.
A follow-up for when the other two PTRACE_SET_SYSCALL_INFO series come
up:
[PATCH v11 0/3] PTRACE_SET_SYSCALL_INFO: add support for seccomp syscall skipping
https://lore.kernel.org/lkml/20261114181923.370930-1-renzo@xxxxxxxxxxx/
[PATCH v4 0/3] ptrace_set_syscall_info: add support for instruction pointer modification
https://lore.kernel.org/lkml/20261114184720.373178-1-renzo@xxxxxxxxxxx/
I tested the full stack on x86_64 (QEMU): this series with your fixup,
then the syscall-skipping v11, then SET_IP v4 (which depends on
syscall-skipping). set_syscall_info passes.
There is one trivial textual conflict: your "#define MAX_ERRNO" lands
right where syscall-skipping v11 patch 3/3 adds new #includes, so it
does not apply with plain "git am"; "git am -3" resolves it, and the
result differs from the stack without your fixup only by the fixup
itself. If you prefer, I can send syscall-skipping v12 rebased on top
of mm-nonmm-unstable.
renzo