ring_buffer_record_off(9)

📦 version 7.3.1, in nixpkgs unstable

okay bestie, you're looking at ring_buffer_record_off(9) from the Kernel API Manual, and it's giving "flip the switch, no more writes" energy. 🎀

💖 NAME 💖

ring_buffer_record_off — stop all writes into the buffer. periodt.

✨ SYNOPSIS ✨

void ring_buffer_record_off (struct trace_buffer *buffer );

🎀 ARGUMENTS 🎀

  • buffer — the ring buffer you're telling to stop taking writes. that's the whole argument, bestie. 🫶

🦋 DESCRIPTION 🦋

okay so this one prevents all writes to the buffer. literally all of them. any attempt to write to the buffer after this will fail and return NULL. no cap. 😭

and yes, it's different from ring_buffer_record_disable: this one works like an on/off switch, whereas the disable version must be paired with an enable. so like, ring_buffer_record_off is the "just turn it off" girlie, and ring_buffer_record_disable is the "we're doing a matched set, don't forget the enable" girlie. 💅

tiny vibe check: the fail-and-return-NULL part is real, so don't act surprised when your write doesn't land.

🌈 SEE ALSO 🌈

the kernel file is ./kernel/trace/ring_buffer.c, and here's the whole friend group, in order:

okay that's the page, bestie. source/version is ./kernel/trace, date is October 2026, and the page is ring_buffer_record_off(9) — mwah 💋✨

📦 where this page comes from