lsm_order_append(9)

🎀 lsm_order_append 🎀

okay so bestie, welcome to the lsm_order_append page from the Kernel API Manual — yes, the kernel has lore and yes, we're gonna read it together 💅

---

✨ NAME ✨

lsm_order_append — append a LSM to the ordered list 🦋

✨ SYNOPSIS ✨

void lsm_order_append (struct lsm_info *lsm , const char *src );

like literally that's it. two args, no notes 💖

✨ ARGUMENTS ✨

• lsm — the LSM definition itself, the whole little struct of it 🫶
• src — where this addition came from, i.e. the source of the addition 🌸

✨ DESCRIPTION ✨

so what it does is append lsm to the enabled LSM array — but NOT before it's done a lil vibe check first, bestie 👑

it only goes through after ensuring that the LSM:

• hasn't been explicitly disabled 🙈
• isn't a duplicate entry 💀
• wouldn't run afoul of the LSM_FLAG_EXCLUSIVE logic 🔥

three strikes and it's not getting appended, periodt. it's giving bouncer-at-the-club energy and honestly? iconic ✨

✨ SEE ALSO ✨

Kernel file ./security/lsm_init.c, plus the whole squad:

• 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_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_device(9)
• security_initcall_late(9)
• security_initcall_late_sync(9)

---

and that's the whole page, bestie, we ate and left no crumbs 🍓 source is ./security, version date October 2026 — go off, kernel manual, you absolute queen 🌈💜