RFC seccomp: drop syscall exit events for rejected syscalls
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest2 patches 2 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | seccomp: introduce seccomp_nack_syscall() helperkernel/ | +10 | 0 replies | |
| 2/2 | seccomp: drop syscall exit events for rejected syscallsinclude/ include/ kernel/ | +14 | 2 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC PATCH 0/2] seccomp: drop syscall exit events for rejected syscalls
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(-)