seccomp_can_sync_threads(9)

💖 seccomp_can_sync_threads(9) — Kernel API Manual 💖

Okay bestie, welcome to the seccomp_can_sync_threads(9) page from the Kernel API Manual — manual name folded in near the top, cute and correct. This one checks if all threads can be synchronized. ✨

🎀 SYNOPSIS 🎀

The whole signature vibe is:

pid_t seccomp_can_sync_threads (void );

🦋 ARGUMENTS 🦋

• void — no arguments. literally none. not a single one. 💅

🌸 DESCRIPTION 🌸

This function expects the sighand and cred_guard_mutex locks to be held. Like, hold those locks first, bestie — that's the assignment. 🔒

It returns 0 on success, -ve on error, or the pid of a thread which was either not in the correct seccomp mode or did not have an ancestral seccomp filter. So yeah: success? 0. Error? -ve. A specific thread being not-correct about seccomp mode or missing an ancestral filter? You get its pid. periodt. 💖

🔥 SEE ALSO 🔥

Bestie, the required reference crew — every single one, no cap:

• Kernel file ./kernel/seccomp.c
• struct seccomp_kaddfd(9)
• struct notification(9)
• struct action_cache(9)
• struct seccomp_filter(9)
• seccomp_check_filter(9)
• seccomp_cache_check_allow(9)
• seccomp_run_filters(9)
• seccomp_filter_release(9)
• seccomp_sync_threads(9)
• seccomp_prepare_filter(9)
• seccomp_prepare_user_filter(9)
• seccomp_is_const_allow(9)
• seccomp_cache_prepare(9)
• seccomp_attach_filter(9)
• seccomp_set_mode_strict(9)
• seccomp_set_mode_filter(9)
• prctl_set_seccomp(9)

mwah 💋 cute little footer moment: source/version is ./kernel, dated October 2026, and the manual page is seccomp_can_sync_threads(9). 🫶✨