aa_path_name(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

Hii bestie, welcome to aa_path_name(9) from the Kernel API Manual! ✨ This one is literally here to get the pathname to a buffer ensure dir / is appended. That's the name energy, preserved and slaying. 🫢

✨ SYNOPSIS ✨

int aa_path_name (const struct path *path , int flags , char *buffer ,
       const char **name , const char **info , const char *disconnected );

🫢 ARGUMENTS 🫢

  • path β€” the path to the file (NOT NULL). πŸ’…
  • flags β€” flags controlling path name generation. ✨
  • buffer β€” buffer to put the name in (NOT NULL). πŸŽ€
  • name β€” Returns - the generated path name if !error (NOT NULL). πŸ‘‘
  • info β€” Returns - information on why the path lookup failed (MAYBE NULL). πŸ¦‹
  • disconnected β€” string to prepend to disconnected paths. 🌸

🌸 DESCRIPTION 🌸

name is a pointer to the beginning of the pathname (which usually differs from the beginning of the buffer), or NULL. πŸ’– If there is an error, name may contain a partial or invalid name that can be used for audit purposes, but it can not be used for mediation. That distinction is important, bestie β€” audit purposes, not mediation. 🚨

We need PATH_IS_DIR to indicate whether the file is a directory or not because the file may not yet exist, and so we cannot check the inode's file type. πŸ¦‹ No cap, that's why it's there. ✨

πŸŽ€ RETURN πŸŽ€

0, else error code if could retrieve name. That's the return section, periodt. πŸ’…

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./security/apparmor/path.c β€” d_namespace_path(9). Go read that too, iykyk. πŸ’œ


xoxo, your aa_path_name(9) bestie πŸ’– β€” source/version: ./security/apparmor, date: October 2026. πŸŽ€

πŸ“¦ where this page comes from