From: Renzo Davoli <renzo@cs.unibo.it>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Oleg Nesterov <oleg@redhat.com>,
"Dmitry V . Levin" <ldv@strace.io>,
Alexey Gladkov <legion@kernel.org>,
Eugene Syromyatnikov <evgsyr@gmail.com>,
Charlie Jenkins <thecharlesjenkins@gmail.com>,
Bradley Morgan <bradley.morgan@linux.dev>,
Shuah Khan <shuah@kernel.org>,
strace-devel@lists.strace.io, linux-api@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v4 2/2] selftests/ptrace: check that PTRACE_SET_SYSCALL_INFO rejects invalid error values
Date: Tue, 17 Nov 2026 10:05:37 +0100 [thread overview]
Message-ID: <avwY4RW14jtVfgZO@cs.unibo.it> (raw)
In-Reply-To: <20261116153642.a8dddc43f53fed0402283dfa@linux-foundation.org>
On Mon, 16 Nov 2026 15:36:42 -0800 Andrew Morton <akpm@linux-foundation.org> wrote:
> LLM suggested a little fixup here, please check.
>
> From: Andrew Morton <akpm@linux-foundation.org>
> Subject: selftests/ptrace: test the lowest valid syscall error
Thanks Andrew, the fixup is correct and a good addition: the test now
covers both sides of the -MAX_ERRNO boundary.
I tested it on top of v4 (x86_64, QEMU): set_syscall_info passes.
Reviewed-by: Renzo Davoli <renzo@cs.unibo.it>
Tested-by: Renzo Davoli <renzo@cs.unibo.it>
renzo
next prev parent reply other threads:[~2026-11-17 9:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 13:40 [PATCH v4 0/2] ptrace: reject out of range error values in PTRACE_SET_SYSCALL_INFO Renzo Davoli
2026-11-16 13:40 ` [PATCH v4 1/2] " Renzo Davoli
2026-11-16 14:03 ` Oleg Nesterov
2026-11-16 13:40 ` [PATCH v4 2/2] selftests/ptrace: check that PTRACE_SET_SYSCALL_INFO rejects invalid error values Renzo Davoli
2026-11-16 23:36 ` Andrew Morton
2026-11-17 9:05 ` Renzo Davoli [this message]
2026-11-17 9:51 ` Renzo Davoli
2026-11-17 15:46 ` Bradley Morgan
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=avwY4RW14jtVfgZO@cs.unibo.it \
--to=renzo@cs.unibo.it \
--cc=akpm@linux-foundation.org \
--cc=bradley.morgan@linux.dev \
--cc=evgsyr@gmail.com \
--cc=ldv@strace.io \
--cc=legion@kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=shuah@kernel.org \
--cc=strace-devel@lists.strace.io \
--cc=thecharlesjenkins@gmail.com \
/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.