ftrace_text_reserved(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ftrace_text_reserved β€” like, the manual page bestie

okay so this is ftrace_text_reserved from the Kernel API Manual, section 9 β€” yes we're in the kernel docs, we're fancy now πŸ’…

✨ NAME ✨

ftrace_text_reserved β€” returns true if a range contains an ftrace location. that's it, that's the whole vibe check πŸ¦‹


πŸŽ€ SYNOPSIS πŸŽ€

int ftrace_text_reserved (const void *start , const void *end );

like, give it two pointers and it'll tell you what's up ✨

🌸 ARGUMENTS 🌸

  • start β€” where your range starts, bestie. the beginning of the range you wanna search 🫢
  • end β€” where your range ends. and inclusive, okay?? end points to the last byte to check, so don't be out here thinking it's exclusive, it is NOT πŸ™ˆ

⭐ RETURN ⭐

returns 1 if start and end contain an ftrace location πŸ”₯

and what counts as an ftrace location? literally just the instruction that's either a NOP or a call to the function tracer. that's the whole criteria, no cap πŸ’€

it checks the ftrace internal tables to figure out if the address belongs or not β€” so it's doing the detective work for you, iconic πŸ‘‘

πŸ’– SEE ALSO πŸ’–

kernel file ./kernel/trace/ftrace.c (iykyk) plus this absolutely unhinged list of friends β€” she knows everyone fr fr:


no pressure but that list is long and every single one of them is a real function, so like... respect the roster 🧚

okay that's the whole page!! thank you for coming to my ted talk πŸ’œ

β€” from ./kernel/trace, dated October 2026, that's a wrap bestie, slay πŸŒˆβœ¨πŸŽ€

πŸ“¦ where this page comes from