get_current_exe(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– get_current_exe(9) πŸ’–

✨ NAME ✨

okay so this is the Kernel API Manual page for get_current_exe β€” it gets the current's executable path, if any. That's the whole vibe: executable path? maybe. bestie, we love a short king. πŸ’…

✨ SYNOPSIS ✨

       const void * get_current_exe (const char **const exe_str , size_t *const
       exe_size );

πŸ’… ARGUMENTS πŸ’…

  • exe_str β€” returned pointer to a path string. Its lifetime is tied to the returned buffer, if any. Cute, but that lifetime note is important, bestie. πŸŽ€
  • exe_size β€” returned size of exe_str, including the trailing null character, if any. Yes, the null counts. ✨

πŸ”₯ RETURN πŸ”₯

Return vibes: you get a pointer to an allocated buffer β€” the buffer that exe_str points to β€” or NULL if there is no executable path, or an error otherwise. That's the trio, periodt. πŸ’€

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./security/landlock/domain.c plus these besties: landlock_unmask_layers(9), landlock_init_layer_masks(9), landlock_merge_ruleset(9), landlock_init_hierarchy_log(9), landlock_get_quiet_optional_accesses(9). Go say hi. πŸ’–


Signed off from the source ./security/landlock, dated October 2026 β€” xoxo, get_current_exe(9) 🫢✨

πŸ“¦ where this page comes from