module_param_named_unsafe(9)

💖 module_param_named_unsafe(9) — Kernel API Manual 💖

okay bestie, welcome to module_param_named_unsafe(9) from the Kernel API Manual — yes, the manual name is right there, we’re being cute and accurate today 🫶

---

🌟 NAME 🌟

module_param_named_unsafe — same as module_param_named but taints kernel 😭

bestie, the “unsafe” is not a vibe check, it taints kernel. It’s literally in the name. 💀

---

✨ SYNOPSIS ✨

the whole call looks exactly like this, no cap:

module_param_named_unsafe (name , value , type , perm );

---

🎀 ARGUMENTS 🎀

• name — a valid C identifier which is the parameter name. so like, actually valid C, bestie — this is the parameter’s name ✨
• value — the actual lvalue to alter. not a copy, the actual lvalue — main character energy 🎯
• type — the type of the parameter. the type, periodt 🦋
• perm — visibility in sysfs. this controls the visibility in sysfs 👑

---

🦋 SEE ALSO 🦋

Kernel file ./include/linux/moduleparam.h says hiii, and the whole friend group is:

• module_param(9)
• module_param_unsafe(9)
• module_param_named(9)
• module_param_cb(9)
• core_param_cb(9)
• postcore_param_cb(9)
• arch_param_cb(9)
• subsys_param_cb(9)
• fs_param_cb(9)
• device_param_cb(9)
• late_param_cb(9)
• core_param(9)
• core_param_unsafe(9)
• __core_param_cb(9)
• module_param_string(9)
• parameq(9)
• parameqn(9)
• module_param_array(9)
• module_param_array_named(9)
• module_param_hw_named(9)
• module_param_hw_array(9)

---

that’s the whole page, bestie 🫶 — from ./include/linux, dated October 2026, and it’s literally module_param_named_unsafe(9). mwah 💋✨