STRUCT TCF_EMATCH_OPS(9)

🌸 NAME 🌸

okay so bestie, this is the Kernel API Manual page for struct tcf_ematch_ops(9), and it's literally the blueprint for ematch module operations. Think of it as the group-chat rules for an ematch module: what it's called, what data it expects, which callbacks it can bring to the party, who owns it, and how it links up. no cap, every member matters. 💅

✨ SYNOPSIS ✨

Here's the whole struct, exactly as it appears:

       struct tcf_ematch_ops {
           int kind;
           int datalen;
           int (*change)(struct net *net, void *, int, struct tcf_ematch *);
           int (*match)(struct sk_buff *, struct tcf_ematch *, struct
       tcf_pkt_info *);
           void (*destroy)(struct tcf_ematch *);
           int (*dump)(struct sk_buff *, struct tcf_ematch *);
           struct module           *owner;
           struct list_head        link;
        };

🫶 Members 🫶

• kind — the identifier (kind) of this ematch module. That's its whole name-tag situation. 🏷️
• datalen — length of expected configuration data (optional). Optional bestie, not mandatory. 🎀
• change — called during validation (optional). Validation-time callback energy. ✨
• match — called during ematch tree evaluation, and it must return 1/0. No vibes-only returns, okay? 😭
• destroy — called during destroyage (optional). Yes, "destroyage" is the word on the page, we respect the lore. 🫡
• dump — called during dumping process (optional). Dump-time callback, slay. 💅
• owner — owner, and it must be set to THIS_MODULE. periodt.
• link — link to previous/next ematch module (internal use). internal-use only, bestie, don't touch unless that's your lane. 🙈

🌈 SEE ALSO 🌈

• Kernel file ./include/net/pkt_cls.h — the file the page points at. iconic.
• tcf_exts_has_actions(9)
• tcf_exts_exec(9)
• struct tcf_pkt_info(9)
• struct tcf_ematch(9)
• struct tcf_ematch_tree(9)
• tcf_em_tree_match(9)

sending you off with a sparkle from source/version ./include/net, dated October 2026 — that's the footer, bestie, not a drill. 💖