From: Christian Loehle <christian.loehle@arm.com>
To: Shuah Khan <shuah@kernel.org>, linux-kselftest@vger.kernel.org
Cc: Rama Krishna Katta <ramakrishna.katta@arm.com>,
Thomas Gleixner <tglx@kernel.org>,
Gregory Price <gourry.memverge@gmail.com>,
Kees Cook <kees@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Andy Lutomirski <luto@kernel.org>,
Gabriel Krisman Bertazi <krisman@collabora.com>,
linux-kernel@vger.kernel.org,
Christian Loehle <christian.loehle@arm.com>
Subject: [PATCH 0/3] selftests: Skip SUD tests when unsupported
Date: Mon, 17 Aug 2026 12:16:08 +0100 [thread overview]
Message-ID: <cover.1786965107.git.christian.loehle@arm.com> (raw)
Syscall User Dispatch (SUD) is unavailable on architectures without
generic syscall entry. Such architectures return -EINVAL for otherwise
valid SUD prctl and ptrace requests, which the SUD selftests currently
report as failures.
Probe SUD with a valid disabled configuration and skip the affected tests
when that probe returns EINVAL. Unexpected errors remain failures, and the
existing coverage is unchanged on kernels that support SUD.
Christian Loehle (3):
selftests/ptrace: Skip get_set_sud if SUD is unsupported
selftests/syscall_user_dispatch: Skip tests if SUD is unsupported
selftests/syscall_user_dispatch: Skip benchmark if SUD is unsupported
tools/testing/selftests/ptrace/get_set_sud.c | 8 +++++
.../syscall_user_dispatch/sud_benchmark.c | 9 +++++
.../syscall_user_dispatch/sud_test.c | 36 +++++++++++++++++++
3 files changed, 53 insertions(+)
base-commit: 8d3ae59288f1e7d58d76558a6ee96d533bc5019f
--
2.34.1
next reply other threads:[~2026-08-17 11:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 11:16 Christian Loehle [this message]
2026-08-17 11:16 ` [PATCH 1/3] selftests/ptrace: Skip get_set_sud if SUD is unsupported Christian Loehle
2026-08-17 11:16 ` [PATCH 2/3] selftests/syscall_user_dispatch: Skip tests " Christian Loehle
2026-08-17 11:16 ` [PATCH 3/3] selftests/syscall_user_dispatch: Skip benchmark " Christian Loehle
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=cover.1786965107.git.christian.loehle@arm.com \
--to=christian.loehle@arm.com \
--cc=gourry.memverge@gmail.com \
--cc=kees@kernel.org \
--cc=krisman@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=ramakrishna.katta@arm.com \
--cc=shuah@kernel.org \
--cc=tglx@kernel.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