From: Stian Halseth <stian@itx.no>
To: Andreas Larsson <andreas@gaisler.com>,
"David S . Miller" <davem@davemloft.net>,
Kees Cook <kees@kernel.org>,
sparclinux@vger.kernel.org
Cc: Andy Lutomirski <luto@amacapital.net>,
Will Drewry <wad@chromium.org>, Oleg Nesterov <oleg@redhat.com>,
Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Stian Halseth <stian@itx.no>
Subject: [PATCH 0/2] sparc64: add seccomp filter support
Date: Wed, 2 Sep 2026 00:08:09 +0200 [thread overview]
Message-ID: <20260901220811.3369666-1-stian@itx.no> (raw)
This adds SECCOMP_FILTER support for sparc64.
The arch prerequisites have been in place for years, so patch 1 is
mostly about the missing piece: letting seccomp veto a syscall, and
returning to user space with the return value the seccomp core set in
pt_regs rather than the -ENOSYS the assembler stubs used to force on
any denied syscall. Patch 2 teaches the seccomp_bpf selftest to
drive sparc64's registers.
Tested on an UltraSPARC T4-1 (sun4v):
- tools/testing/selftests/seccomp/seccomp_bpf: 95 passed, 0 failed,
16 skipped (uprobes and other optional features)
- libseccomp with its pending SPARC support (libseccomp PR #471)
passes its full suite, 5190 of 5190, including the live tests
that require kernel SECCOMP_FILTER
- docker containers run confined by the default profile, and a
custom SCMP_ACT_ERRNO profile denies as expected
The libseccomp side is https://github.com/seccomp/libseccomp/pull/471,
and the tracking issue is https://github.com/sparclinux/issues/issues/11.
Stian Halseth (2):
sparc64: add seccomp filter support
selftests/seccomp: add sparc64 support
arch/sparc/Kconfig | 2 +-
arch/sparc/include/asm/seccomp.h | 15 ++++++++
arch/sparc/include/asm/syscall.h | 11 +++---
arch/sparc/kernel/entry.h | 2 +-
arch/sparc/kernel/ptrace_64.c | 28 ++++++++++-----
arch/sparc/kernel/syscalls.S | 28 +++++++++++----
tools/testing/selftests/seccomp/seccomp_bpf.c | 35 +++++++++++++++++++
7 files changed, 98 insertions(+), 23 deletions(-)
--
2.45
next reply other threads:[~2026-09-01 22:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 22:08 Stian Halseth [this message]
2026-09-01 22:08 ` [PATCH 1/2] sparc64: add seccomp filter support Stian Halseth
2026-09-01 22:08 ` [PATCH 2/2] selftests/seccomp: add sparc64 support Stian Halseth
2026-09-02 0:02 ` Kees Cook
2026-09-02 7:15 ` Stian Halseth
2026-09-02 7:21 ` Stian Halseth
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=20260901220811.3369666-1-stian@itx.no \
--to=stian@itx.no \
--cc=andreas@gaisler.com \
--cc=davem@davemloft.net \
--cc=glaubitz@physik.fu-berlin.de \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=oleg@redhat.com \
--cc=shuah@kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=wad@chromium.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.