aa_dfa_next(9)

✨ NAME ✨

aa_dfa_next — step one character to the next state in the dfa

okay so this little cutie is from the Kernel API Manual, and the whole vibe is: take a dfa, take a state, take one input character, and step to the next state. Bestie, it’s giving “one tiny step in the dfa journey,” slay. 💅✨

💅 SYNOPSIS 💅

aa_state_t aa_dfa_next (const struct aa_dfa *dfa , aa_state_t state ,
       const char c );

✨ ARGUMENTS ✨

• dfa — the dfa to traverse (NOT NULL, so do not come in here with a null, bestie 🙅‍♀️).
• state — the state to start in.
• c — the input character to transition on.

🦋 DESCRIPTION 🦋

The DESCRIPTION text literally says: aa_dfa_match will step through the dfa by one input character c.

Yes, it says aa_dfa_match even though the page is aa_dfa_next — I’m just relaying the lore, not editing it. No cap. 😭✨

🎀 RETURN 🎀

What comes back is: state reach after input c. That’s exactly the phrase on the page, bestie — state reach after input c. 🫶

🔥 SEE ALSO 🔥

• Kernel file ./security/apparmor/match.c
• unpack_table(9)
• verify_table_headers(9)
• verify_dfa(9)
• dfa_free(9)
• aa_dfa_free_kref(9)
• remap_data16_to_data32(9)
• aa_dfa_unpack(9)
• aa_dfa_match_len(9)
• aa_dfa_match(9)
• aa_dfa_match_until(9)
• aa_dfa_matchn_until(9)
• aa_dfa_leftmatch(9)

big sparkly sign-off: source/version energy is ./security/apparmor, the date is October 2026, and the page is aa_dfa_next(9). 💖✨🎀