edac_get_owner(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… edac_get_owner(9) β€” the Kernel API Manual, but make it make sense

okay bestie, welcome to edac_get_owner, a tiny little function in the Kernel API Manual that takes zero arguments and tells you exactly one thing. no cap, it's giving "small but mighty" πŸ’–


✨ NAME ✨

edac_get_owner β€” returns the owner's mod_name of EDAC MC 🫢

like, it's the little function whose whole personality is "whose module is this, actually?" and honestly? respect.


🌸 SYNOPSIS 🌸

const char * edac_get_owner (void );

that's it. that's the whole vibe. a const char * and a void and zero drama ✨


πŸŽ€ ARGUMENTS πŸŽ€

  • void β€” no arguments πŸ’€ literally none. nothing. the void is the point. you show up, you pass nothing, and it's fine. iconique.

πŸ¦‹ RETURN πŸ¦‹

so here's what you get back, and there are exactly two (2) outcomes, bestie, keep up πŸ‘‘

  • a pointer to the mod_name string β€” this happens when EDAC MC is owned πŸŽ‰
  • NULL β€” this happens otherwise πŸ™ˆ

that's the whole return contract. no structs, no error codes, no little surprise extras. if it's owned you get the string, if it isn't you get NULL, and you will be checking that NULL before you dereference it because we are not about that segfault life fr fr πŸ’…

heads up queen: NULL is a real, expected return value here β€” it is not an error code, it just means "not owned". check before you use it, every single time 😭

🌈 SEE ALSO 🌈

the whole friend group shows up here, and they all live in the kernel file ./drivers/edac/edac_mc.h 🧚:

go read those next, they're literally the rest of the lore πŸ“šβœ¨


and that's the page, bestie!! πŸ₯³ this one comes from ./drivers/edac, dated October 2026 β€” so if you're reading it, just know the EDAC girls were serving kernel documentation back in October 2026 and we are still obsessed πŸ’–πŸŽ€πŸ¦‹ slay, stay hydrated, and always check your pointers 🫢

πŸ“¦ where this page comes from