__next_profile(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

okay so bestie, this is the __next_profile(9) page from the Kernel API Manual β€” it’s the function that steps to the next profile in a profile tree. Slay.

✨ SYNOPSIS ✨

struct aa_profile * __next_profile (struct aa_profile *p );

πŸŽ€ ARGUMENTS πŸŽ€

  • p β€” the current profile in the tree, and bestie it is NOT NULL. Like, do not come in here with a NULL, fr fr.

πŸ’… DESCRIPTION πŸ’…

It performs a depth first traversal on the profile tree in a namespace. That’s the whole vibe: depth first, profile tree, namespace, next profile energy. Periodt.

πŸ”₯ RETURN πŸ”₯

It gives you the next profile, or NULL if it’s done. Requires: profile->ns.lock to be held β€” no cap, hold that lock. πŸ’€

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./security/apparmor/apparmorfs.c plus the whole friend group: mangle_name(9), __aafs_setup_d_inode(9), aafs_create(9), aafs_create_file(9), aafs_create_dir(9), aafs_remove(9), aa_simple_write_to_buffer(9), aa_get_data_from_compressed(9), query_data(9), query_label(9), aa_write_access(9), __next_ns(9), __first_profile(9), next_profile(9), p_start(9), p_next(9), p_stop(9), seq_show_profile(9), entry_create_file(9), entry_create_dir(9), entry_remove_file(9), entry_remove_dir(9), aa_destroy_aafs(9), aa_create_aafs(9).


Cute sign-off: this page lives in ./security/apparmor, stamped October 2026, and it’s giving kernel API manual realness. πŸ’–βœ¨πŸ«Ά

πŸ“¦ where this page comes from