From: Gabriel Krisman Bertazi <krisman@suse.de>
To: Christian Loehle <christian.loehle@arm.com>,
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: Re: [PATCH 0/3] selftests: Skip SUD tests when unsupported
Date: Fri, 04 Sep 2026 13:45:44 -0300 [thread overview]
Message-ID: <87jyp12cef.fsf@mailhost.krisman.be> (raw)
In-Reply-To: <cover.1786965107.git.christian.loehle@arm.com>
Christian Loehle <christian.loehle@arm.com> writes:
> 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.
Reviewed-by: Gabriel Krisman Bertazi <krisman@suse.de>
--
Gabriel Krisman Bertazi
prev parent reply other threads:[~2026-09-04 16:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 11:16 [PATCH 0/3] selftests: Skip SUD tests when unsupported Christian Loehle
2026-08-17 11:16 ` [PATCH 1/3] selftests/ptrace: Skip get_set_sud if SUD is unsupported Christian Loehle
2026-08-26 21:58 ` Gregory Price
2026-08-17 11:16 ` [PATCH 2/3] selftests/syscall_user_dispatch: Skip tests " Christian Loehle
2026-08-26 22:00 ` Gregory Price
2026-08-17 11:16 ` [PATCH 3/3] selftests/syscall_user_dispatch: Skip benchmark " Christian Loehle
2026-08-26 22:01 ` Gregory Price
2026-08-26 14:56 ` [PATCH 0/3] selftests: Skip SUD tests when unsupported Christian Loehle
2026-09-13 10:24 ` Christian Loehle
2026-09-04 16:45 ` Gabriel Krisman Bertazi [this message]
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=87jyp12cef.fsf@mailhost.krisman.be \
--to=krisman@suse.de \
--cc=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 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.