tcf_em_tree_dump(9)

✨ tcf_em_tree_dump — Kernel API Manual ✨

okay so bestie, you know how we're always like "the ematch tree is so iconic, someone should write it down"? yeah. this is the function that does exactly that. it's tcf_em_tree_dump, it lives in the kernel API manual, and honestly? she ate. 💅

---

🌸 SYNOPSIS 🌸

int tcf_em_tree_dump(struct sk_buff *skb, struct tcf_ematch_tree *tree, int tlv);

that's the whole signature, no cap. three args, one int back. let's break it down. 🎀

---

🦋 ARGUMENTS 🦋

• skb — the sk_buff that's holding the rtnl message. she's the carrier, the vessel, the main character's ride. 🚗
• tree — the ematch tree that's getting dumped. this is the actual content, the moment, the reason we're all here.
• tlv — the TLV type that gets used to encapsulate the tree. like the cute little wrapper the tree gets swaddled in. 🎁

---

👑 DESCRIPTION 👑

so what does she do? this function dumps an ematch tree into an rtnl message. that's it, that's the gig. 💖

and here's the lowkey iconic part: it is valid to call this function while the ematch tree is in use. you don't have to freeze everything and shoo people away first. she's chill like that. 🧚

now for the vibe check that matters: Returns -1 if the skb tailroom is insufficient. so if there's not enough room at the end of the skb, she's not gonna fake it — you get -1 and that's your answer. no cap. 💀

nothing about the return value otherwise gets promised here, bestie, so don't go inventing one. we report what the manpage reports, periodt.

---

🌈 SEE ALSO 🌈

• Kernel file ./net/sched/ematch.c
• tcf_em_register(9)
• tcf_em_unregister(9)
• tcf_em_tree_validate(9)
• tcf_em_tree_destroy(9)

like, the whole friend group. go say hi. 🫶

---

and that's the page!! she comes from ./net/sched, dated October 2026, and no I will not be normal about a kernel function with this much main character energy. mwah. 💜✨