ring_buffer_record_enable(9)

💖 NAME 💖

okay bestie, welcome to the Kernel API Manual page for ring_buffer_record_enable(9) ✨

ring_buffer_record_enable — enable writes to the buffer. That’s literally her whole job: she turns the writing vibe back on for the ring buffer 💅

✨ SYNOPSIS ✨

void ring_buffer_record_enable (struct trace_buffer *buffer );

🫶 ARGUMENTS 🫶

• buffer — the ring buffer to enable writes. That’s the one you’re giving main-character energy to 💖

🌸 DESCRIPTION 🌸

So here’s the tea, bestie: multiple disables will need the same number of enables to truly enable the writing (much like preempt_disable). No cap — count them carefully, because one enable doesn’t magically cancel a whole stack of disables 🙈

⚠️ important vibe check: if you disabled it more than once, you need that same number of enables to actually get writing back on. periodt.

👀 SEE ALSO 👀

Kernel file: ./kernel/trace/ring_buffer.c — that’s the home base, bestie 🏠✨

The whole ring-buffer friend group, in order:

• ring_buffer_event_length(9), ring_buffer_event_data(9), rb_page_capacity(9), rb_subbuf_capacity(9), rb_subbuf_max_data_size(9), rb_subbuf_start(9)
• ring_buffer_event_time_stamp(9), ring_buffer_nr_dirty_pages(9), ring_buffer_wake_waiters(9), ring_buffer_wait(9), ring_buffer_poll_wait(9), rb_check_pages(9), rb_validate_buffer(9)
• __ring_buffer_alloc(9), __ring_buffer_alloc_range(9), __ring_buffer_alloc_remote(9), ring_buffer_free(9), ring_buffer_resize(9), rb_update_event(9), ring_buffer_nest_start(9), ring_buffer_nest_end(9), ring_buffer_unlock_commit(9), ring_buffer_lock_reserve(9), ring_buffer_discard_commit(9), ring_buffer_write(9)
• ring_buffer_record_disable(9), ring_buffer_record_off(9), ring_buffer_record_on(9), ring_buffer_record_is_on(9), ring_buffer_record_is_set_on(9), ring_buffer_record_is_on_cpu(9), ring_buffer_record_disable_cpu(9), ring_buffer_record_enable_cpu(9)
• ring_buffer_oldest_event_ts(9), ring_buffer_bytes_cpu(9), ring_buffer_entries_cpu(9), ring_buffer_overrun_cpu(9), ring_buffer_commit_overrun_cpu(9), ring_buffer_dropped_events_cpu(9), ring_buffer_read_events_cpu(9), ring_buffer_entries(9), ring_buffer_overruns(9)
• ring_buffer_iter_reset(9), ring_buffer_iter_empty(9), ring_buffer_peek(9), ring_buffer_iter_peek(9), ring_buffer_consume(9), ring_buffer_read_start(9), ring_buffer_read_finish(9), ring_buffer_iter_advance(9), ring_buffer_size(9), ring_buffer_max_event_size(9)
• ring_buffer_reset_cpu(9), ring_buffer_reset_online_cpus(9), ring_buffer_reset(9), ring_buffer_empty(9), ring_buffer_empty_cpu(9), ring_buffer_swap_cpu(9)
• ring_buffer_alloc_read_page(9), ring_buffer_free_read_page(9), ring_buffer_read_page(9), ring_buffer_read_page_data(9), ring_buffer_read_page_size(9), ring_buffer_subbuf_size_get(9), ring_buffer_subbuf_order_get(9), ring_buffer_subbuf_order_set(9)

xoxo 💋 this page’s source/version is ./kernel/trace, dated October 2026, and it’s literally ring_buffer_record_enable(9). slay ✨🦋