ENUM KMOD_TEST_CASE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ enum kmod_test_case(9) ✨

okay so this is from the Kernel API Manual bestie, and it's all about enum kmod_test_case β€” the linker table test case situation πŸ’… like it's genuinely a kernel thing, not a drill.


🌸 NAME 🌸

enum kmod_test_case β€” the linker table test case, periodt πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

enum kmod_test_case {
    TEST_KMOD_DRIVER ,
    TEST_KMOD_FS_TYPE

};

no cap, that's the whole enum, two constants, she's compact πŸ‘‘


πŸ’– Constants πŸ’–

  • TEST_KMOD_DRIVER β€” stress tests request_module πŸ”₯ like it's literally putting request_module through the vibe check
  • TEST_KMOD_FS_TYPE β€” stress tests get_fs_type ⭐ same energy, different function, she's stressing get_fs_type fr fr

🌈 Description 🌈

so if you add a test case β€” and honestly slay if you do β€” please be sure to review whether you need to set need_mod_put for your test case πŸ™ˆ like don't just drop a new constant in and ghost, check that need_mod_put situation first, iykyk πŸ’€

ok bestie this is the one thing the page actually asks of you: review need_mod_put for your test case when you add one. not optional-vibes, it's giving "please actually check" 🫢

🧚 SEE ALSO 🧚

  • Kernel file ./lib/test_kmod.c πŸ“
  • struct kmod_test_device_info(9) πŸ’œ
  • struct kmod_test_device(9) ✨

and that's the whole page, bestie πŸ“ sign-off time: this lil icon lives in ./lib, dated October 2026, and it's enum kmod_test_case(9) all the way down πŸ’–πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from