[RFC PATCH 0/2] seccomp: drop syscall exit events for rejected syscalls

Oleg Nesterov
2026-04-19T15:53:00Z

On top of [tip: core/urgent] entry: Kill ARCH_SYSCALL_WORK_{ENTER,EXIT}
https://git.kernel.org/tip/7b41ff29c8d386257bae62ad557fd6bad8cc6787

Still RFC, please comment...

Of course this is a user-visible behavior change. ptrace and audit
will no longer see the paired exit events for syscalls rejected with
force_sig_seccomp(). I _hope_ this is fine and better than what we
have now. If this is not acceptable, we can return to "seccomp: defer
syscall_rollback() to get_signal()" we discussed before.

2/2 currently ignores !CONFIG_GENERIC_ENTRY architectures. If this
approach is accepted, it will be simple to update them one-by-one
to sync with the CONFIG_GENERIC_ENTRY case.

Oleg.
---

include/linux/entry-common.h | 9 ++++++++-
include/linux/thread_info.h | 2 ++
kernel/seccomp.c | 22 ++++++++++++++--------
3 files changed, 24 insertions(+), 9 deletions(-)