traceprobe_parse_event_name(9)

✨ traceprobe_parse_event_name(9) ✨

okay so bestie, welcome to the kernel API manual page for traceprobe_parse_event_name(9) — yes that's the whole title, it's giving "function so important it gets its own little paper" 💅

---

🌸 NAME 🌸

traceprobe_parse_event_name — parses a string into group and event names 🎀

---

🦋 SYNOPSIS 🦋

int traceprobe_parse_event_name (const char **pevent , const char
**pgroup , char *buf , int offset );

---

💖 ARGUMENTS 💖

• pevent — a pointer to the string that's gonna get parsed, the main character of this whole operation ✨
• pgroup — a pointer to the group name 🫶
• buf — a buffer where we stash the parsed group name 💐
• offset — the offset of the string in the original user command, and it's literally only there for logging purposes, no cap 📝

---

🔥 DESCRIPTION 🔥

so what this does is it parses a string that's formatted like [GROUP/][EVENT] or [GROUP.][EVENT] — and heads up bestie, either GROUP or EVENT or both must be specified, you can't just roll up with nothing 🙈

because the parsed group name gets stored in buf, the caller has to make sure buf is at least MAX_EVENT_NAME_LEN bytes. that's on you, not on this function, so like… don't skip the vibe check on your buffer size 💀

if it succeeds, *pevent gets updated to point to the event name part of the original string, or NULL if there's no event name. also, *pgroup gets updated to point to the parsed group, which is the one stored in buf, or NULL if there's no group name. slay 👑

---

⭐ RETURN ⭐

0 on success, or -EINVAL on failure 😭

---

🌈 SEE ALSO 🌈

Kernel file ./kernel/trace/trace_probe.c — go read it, iykyk 💜

---

and that's the page fr fr 🧚 from ./kernel/trace, the October 2026 edition — mwah, go parse some event names bestie 💅💖🌸