This adds the ability for threads to request seccomp filter synchronization across their thread group (at filter attach time). For example, for Chrome to make sure graphic driver threads are fully confined after seccomp filters have been attached.
To support this, locking on seccomp changes via thread-group-shared sighand lock is introduced, along with refactoring of no_new_privs. Races with thread creation are handled via delayed duplication of the seccomp task struct field and cred_guard_mutex. This includes a new syscall (instead of adding a new prctl option), as suggested by Andy Lutomirski and Michael Kerrisk. Thanks! -Kees v10: - dropped pending-kill checks (oleg) - tweaked memory barriers (oleg) v9: - rearranged/split patches to make things more reviewable - added use of cred_guard_mutex to solve exec race (oleg, luto) - added barriers for TIF_SECCOMP vs seccomp.mode race (oleg, luto) - fixed missed copying of nnp state after v8 refactor (oleg) v8: - drop use of tasklist_lock, appears redundant against sighand (oleg) - reduced use of smp_load_acquire to logical minimum (oleg) - change nnp to a task struct held atomic flags field (oleg, luto) - drop needless irqflags changes in fork.c for holding sighand lock (oleg) - cleaned up use of thread for-each loop (oleg) - rearranged patch order to keep syscall changes adjacent - added example code to manpage (mtk) v7: - rebase on Linus's tree (merged with network bpf changes) - wrote manpage text documenting API (follows this series) v6: - switch from seccomp-specific lock to thread-group lock to gain atomicity - implement seccomp syscall across all architectures with seccomp filter - clean up sparse warnings around locking v5: - move includes around (drysdale) - drop set_nnp return value (luto) - use smp_load_acquire/store_release (luto) - merge nnp changes to seccomp always, fewer ifdef (luto) v4: - cleaned up locking further, as noticed by David Drysdale v3: - added SECCOMP_EXT_ACT_FILTER for new filter install options v2: - reworked to avoid clone races -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
