ne_sanity_c...r_mem_region(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ NAME πŸŽ€

okay so bestie, this is the ne_sanity_check_user_mem_region(9) page from the Kernel API Manual ✨ and it does exactly what it says on the tin: it sanity-checks the user space memory region that showed up during the set user memory region ioctl call. no cap, that's the whole vibe πŸ’…


🌸 SYNOPSIS 🌸

int ne_sanity_check_user_mem_region (struct ne_enclave *ne_enclave ,
struct ne_user_memory_region mem_region );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • ne_enclave β€” private data associated with the current enclave. it's giving "main character struct" energy πŸ‘‘
  • mem_region β€” the user space memory region that needs to be sanity checked. yes, this is the one getting the vibe check πŸ”

πŸ’œ CONTEXT πŸ’œ

Process context. This function is called with the ne_enclave mutex held. like, the lock is already in the group chat, bestie β€” don't double-text it 🫢

✨ RETURN ✨

  • 0 on success β€” slay, everything checks out πŸ’–
  • A negative return value on failure β€” not iconic, but important 😭

🌈 SEE ALSO 🌈


source/version check, bestie: this page's source/version is ./drivers/virt/nitro_enclaves, and it's dated October 2026 πŸ—“οΈπŸ’– mwah, go read the other refs, ily πŸ’‹βœ¨

πŸ“¦ where this page comes from