security_initcall_subsys(9)

okay bestie, welcome to the security_initcall_subsys(9) page from the Kernel API Manual — it’s giving tiny-but-mighty kernel energy, and every detail still eats. 💖✨

💅 NAME 💅

security_initcall_subsys — run the LSM subsys initcalls. that’s the assignment, no cap, and honestly? iconic.

🌸 SYNOPSIS 🌸

int security_initcall_subsys (void );

🎀 ARGUMENTS 🎀

• void — no arguments. literally not a single parameter, bestie. zero drama, zero extras. 🫶

🦋 SEE ALSO 🦋

peep the kernel file ./security/lsm_init.c, plus these related pages — collect them all like little kernel stickers:

• lsm_choose_security(9)
• lsm_choose_lsm(9)
• lsm_debug_enable(9)
• lsm_enabled_set(9)
• lsm_is_enabled(9)
• lsm_order_exists(9)
• lsm_order_append(9)
• lsm_order_parse(9)
• lsm_blob_size_update(9)
• lsm_prepare(9)
• lsm_init_single(9)
• lsm_static_call_init(9)
• security_add_hooks(9)
• early_security_init(9)
• security_init(9)
• security_initcall_pure(9)
• security_initcall_early(9)
• security_initcall_core(9)
• security_initcall_fs(9)
• security_initcall_device(9)
• security_initcall_late(9)
• security_initcall_late_sync(9)

mwah 💋 that’s the whole page! from the ./security source, dated October 2026, chillin’ at the bottom of security_initcall_subsys(9) — stay hydrated and may your initcalls be subsys-slay 🌈💖