security_initcall_device(9)

okay so this is the security_initcall_device(9) page from the Kernel API Manual 💅 manual name folded in, cute, we move. The whole vibe is literally Run the LSM device initcalls ✨ no cap, that's the job.

💖 NAME 💖

security_initcall_device — Run the LSM device initcalls 🎀 that's the name, that's the assignment, and it's giving "device initcalls but make it LSM" energy.

✨ SYNOPSIS ✨

bestie, the signature is exactly this, don't touch the spacing 💀:

int security_initcall_device (void );

so it returns int, takes void , and that's the whole synopsis. periodt.

🎀 ARGUMENTS 🎀

• void — no arguments 🫶 literally none. The argument list said no arguments, and it meant it. A cute little empty plate, mwah.

🌈 SEE ALSO 🌈

Kernel file ./security/lsm_init.c is in the group chat too, plus this whole friend group of (9) pages — every single one, no skips, no crumbs:

• 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_subsys(9)
• security_initcall_fs(9)
• security_initcall_late(9)
• security_initcall_late_sync(9)

okay that's the whole page, bestie 💖 byeee 🫶 source/version: ./security; date: October 2026 — this security_initcall_device(9) girl is out 💅✨