ignore_event(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– ignore_event(9) β€” Kernel API Manual πŸ’–

✨ NAME ✨

ignore_event β€” Check dereferenced fields while writing to the seq buffer. Bestie, this is the field-safety vibe check for the seq buffer. πŸ‘‘

πŸŽ€ SYNOPSIS πŸŽ€

bool ignore_event (struct trace_iterator *iter );

🌸 ARGUMENTS 🌸

  • iter β€” The iterator that holds the seq buffer and the event being printed. That's the main character carrying both the seq buffer and the event.

πŸ’… DESCRIPTION πŸ’…

At boot up, test_event_printk will flag any event that dereferences a string with "s" that does exist in the ring buffer. It may still be valid, as the string may point to a static string in the kernel rodata that never gets freed. But if the string pointer is pointing to something that was allocated, there's a chance that it can be freed by the time the user reads the trace. This would cause a bad memory access by the kernel and possibly crash the system. πŸ’€

No cap, this function will check if the event has any fields flagged as needing to be checked at runtime and perform those checks.

If it is found that a field is unsafe, it will write into the iter->seq a message stating what was found to be unsafe. So you get the receipts right in the seq buffer. 🧚

πŸ”₯ RETURN πŸ”₯

true if the event is unsafe and should be ignored; false otherwise. That's the whole read. πŸ’…

🌈 SEE ALSO 🌈

Kernel file ./kernel/trace/trace.c β€” plus the whole squad:

πŸ’– okay that's the page, bestie! From ./kernel/trace Β· October 2026 Β· ignore_event(9) β€” periodt, slay, and may your fields always be safe βœ¨πŸ’…

πŸ“¦ where this page comes from