is_module_address(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– is_module_address β€” kernel API manual, but make it make sense πŸ’–

okay so real talk, we're in the is_module_address(9) page of the Kernel API Manual, and honestly? it's a short one. a little baby page. but it's important, so grab your iced coffee and let's go πŸ“


✨ NAME ✨

is_module_address β€” literally just: is this address inside a module? that's it. that's the whole vibe check 🫢


✨ SYNOPSIS ✨

bool is_module_address (unsigned long addr );

it hands you back a bool, no cap β€” so you're getting a yes or a no, nothing in between πŸ’…


🌸 ARGUMENTS 🌸

  • addr β€” the address you wanna check. that's the one. that's the address. drop it in and let the function do its little investigation πŸ”

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the thing bestie β€” if what you actually wanna know is whether the address is code and not data, then you don't want this function, you want to go see is_module_text_address. that's the one for the code-only question. this page is just pointing you there, and honestly? respect. it knows its limits 😌

no like genuinely, that's the whole description. short king behavior πŸ‘‘

πŸ‘‘ SEE ALSO πŸ‘‘

okay this is the part where it goes off. the kernel file to look at is ./kernel/module/main.c, and then there's a whole friend group of pages:

like, the whole elf_validity_cache_* squad showed up. iconic. they ate and left no crumbs 🌈⭐


and that's the page!! mwah πŸ’‹ signed off from ./kernel/module, dated October 2026, author of record is_module_address(9) β€” okay bye, ily, go check your module addresses responsibly πŸŽ€πŸ’œ

πŸ“¦ where this page comes from