module_param_cb(9)
β¨ module_param_cb β¨
Okay so bestie, welcome to the Kernel API Manual β this is the page for module_param_cb(9), and honestly? It's giving main character energy for module/cmdline parameters. Let's get into it π
πΈ NAME πΈ
module_param_cb β the general callback for a module/cmdline parameter. Like, the general one. The callback of all callbacks. Periodt π«Ά
π¦ SYNOPSIS π¦
module_param_cb (name , ops , arg , perm );
That's the whole vibe. Four args, no cap.
π ARGUMENTS π
nameβ a valid C identifier which is the parameter name. Gotta be valid C, bestie, we're not out here inventing syntax πopsβ the set & get operations for this parameter. Your getters and setters, the whole little operation duo β¨argβ args for ops. The stuff you're passing along to those operations, iykyk.permβ visibility in sysfs. How visible this parameter is in sysfs β your whole visibility moment π
π₯ DESCRIPTION π₯
The ops can have NULL set or get functions. That's it. That's the whole description. Lowkey iconic of them to keep it that short, ngl π
π SEE ALSO π
- Kernel file
./include/linux/moduleparam.h module_param(9)module_param_unsafe(9)module_param_named(9)module_param_named_unsafe(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)
Look at that whole friend group of parameter functions β obsessed, fr fr π
And that's the page, bestie! This one lives in ./include/linux and it's dated October 2026. Go forth and register your parameters, slay style πΈπ§π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms