fgraph_get_task_var(9)

💅 fgraph_get_task_var(9) — from the Kernel API Manual, bestie

Okay so real talk, this one lives in section 9 of the Kernel API Manual and it's called fgraph_get_task_var. It's short, it's sweet, and it does literally one thing. Let's get into it ✨

---

🌸 NAME 🌸

fgraph_get_task_var — retrieve a task specific state variable 🎀

Like, it goes and gets you a per-task variable. That's the whole vibe check.

---

✨ SYNOPSIS ✨

unsigned long * fgraph_get_task_var (struct fgraph_ops *gops );

One function, one argument, returns a pointer. Iconic, honestly. No notes. 👑

---

🦋 ARGUMENTS 🦋

• gops — the ftrace_ops that owns the task specific variable 💖. Yes bestie, this is the struct whose variable you're asking about, so don't just hand it any old thing.

---

💜 DESCRIPTION 💜

So here's the tea 🌈: every registered fgraph_ops has a task state variable reserved on the task's ret_stack. Like, it's already there, sitting pretty, minding its own business. This function returns the address to that variable — that's it, that's the job 🫶

To say it again in a slightly more formal font: it returns the address to the fgraph_ops gops tasks specific unsigned long variable. So what you get back is an unsigned long *, pointing right at that per-task state. Slay. 💅

Ngl, "returns the address to the fgraph_ops gops tasks specific unsigned long variable" is the whole description — the original doesn't say anything more, so neither will I. No made-up lore here, bestie 🙈

---

🔥 SEE ALSO 🔥

Go check the kernel file ./kernel/trace/fgraph.c — that's the main character 🧚 — plus these absolute legends:

• fgraph_reserve_data(9)
• fgraph_retrieve_data(9)
• fgraph_retrieve_parent_data(9)
• ftrace_graph_stop(9)
• ftrace_graph_get_ret_stack(9)
• ftrace_graph_top_ret_addr(9)
• ftrace_graph_ret_addr(9)

---

And that's the page, bestie 💖 It ships out of ./kernel/trace, dated October 2026, and it lives under the name fgraph_get_task_var(9) — go forth and grab those task vars, you've got this 🌟🍓