tracing_cond_snapshot_data(9)

💅 tracing_cond_snapshot_data(9) 💅

okay so hi bestie!! welcome to the tracing_cond_snapshot_data page from the Kernel API Manual — yes it's a whole section 9 function and yes it's lowkey iconic. grab a strawberry 🍓 and let's get into it.

---

✨ NAME ✨

tracing_cond_snapshot_data — the little accessor that gets you the user data hanging out with a snapshot 🫶

---

🎀 SYNOPSIS 🎀

void * tracing_cond_snapshot_data (struct trace_array *tr );

that's it. that's the whole vibe check. 💅

---

🌸 ARGUMENTS 🌸

• tr — the tracing instance, bestie. the trace array. the main character of this whole function. 👑

---

🦋 DESCRIPTION 🦋

okay so picture this: the user enables a conditional snapshot using tracing_snapshot_cond_enable, right? and when they do that, their user-defined cond_data gets saved right along with the snapshot. literally packaged up together. 🎁

this accessor? it's the thing you call to retrieve that cond_data. that's its whole job. it ate, honestly.

⚠️ do NOT call this from cond_snapshot.update — no cap. it takes the tr->max_lock lock, and the code calling cond_snapshot.update has already taken that lock. so you'd be doubling up on it and it's giving 💀 deadlock energy. just don't.

and what does it hand back? the cond_data associated with the trace array's snapshot. periodt. ✨

---

🔥 SEE ALSO 🔥

• kernel file ./kernel/trace/trace_snapshot.c — that's where the magic lives 🧚
• tracing_snapshot_cond(9)
• tracing_snapshot_alloc(9)
• tracing_snapshot_cond_enable(9)
• tracing_snapshot_cond_disable(9)
• update_max_tr(9)
• update_max_tr_single(9)

all of these are sisters, read them together iykyk 📚💜

---

and that's the page!! 💖 this one lives in ./kernel/trace, dated October 2026 — bye bestie, go take some snapshots responsibly 🌈⭐