Linux Trace Kernel
 help / color / mirror / Atom feed
From: Vincent Donnefort <vdonnefort@google.com>
To: rostedt@goodmis.org, mhiramat@kernel.org,
	 linux-trace-kernel@vger.kernel.org
Cc: mathieu.desnoyers@efficios.com, kernel-team@android.com,
	 linux-kernel@vger.kernel.org,
	Vincent Donnefort <vdonnefort@google.com>
Subject: [PATCH v3 10/18] ring-buffer: Use panic-friendly locking in ring_buffer_iter interface
Date: Tue, 21 Jul 2026 11:35:55 +0100	[thread overview]
Message-ID: <20260721103603.342266-11-vdonnefort@google.com> (raw)
In-Reply-To: <20260721103603.342266-1-vdonnefort@google.com>

In preparation for allowing trace_remote to dump the buffer on panic,
make the non-consuming iterator functions panic-friendly.

Signed-off-by: Vincent Donnefort <vdonnefort@google.com>

diff --git a/kernel/trace/ring_buffer.c b/kernel/trace/ring_buffer.c
index f970d461b2ba..517bdb061083 100644
--- a/kernel/trace/ring_buffer.c
+++ b/kernel/trace/ring_buffer.c
@@ -5601,6 +5601,9 @@ static void rb_iter_reset(struct ring_buffer_iter *iter)
 	}
 }
 
+static inline bool rb_reader_lock(struct ring_buffer_per_cpu *cpu_buffer);
+static inline void rb_reader_unlock(struct ring_buffer_per_cpu *cpu_buffer, bool locked);
+
 /**
  * ring_buffer_iter_reset - reset an iterator
  * @iter: The iterator to reset
@@ -5612,15 +5615,18 @@ void ring_buffer_iter_reset(struct ring_buffer_iter *iter)
 {
 	struct ring_buffer_per_cpu *cpu_buffer;
 	unsigned long flags;
+	bool dolock;
 
 	if (!iter)
 		return;
 
 	cpu_buffer = iter->cpu_buffer;
 
-	raw_spin_lock_irqsave(&cpu_buffer->reader_lock, flags);
+	local_irq_save(flags);
+	dolock = rb_reader_lock(cpu_buffer);
 	rb_iter_reset(iter);
-	raw_spin_unlock_irqrestore(&cpu_buffer->reader_lock, flags);
+	rb_reader_unlock(cpu_buffer, dolock);
+	local_irq_restore(flags);
 }
 EXPORT_SYMBOL_GPL(ring_buffer_iter_reset);
 
@@ -6297,11 +6303,14 @@ ring_buffer_iter_peek(struct ring_buffer_iter *iter, u64 *ts)
 	struct ring_buffer_per_cpu *cpu_buffer = iter->cpu_buffer;
 	struct ring_buffer_event *event;
 	unsigned long flags;
+	bool dolock;
 
  again:
-	raw_spin_lock_irqsave(&cpu_buffer->reader_lock, flags);
+	local_irq_save(flags);
+	dolock = rb_reader_lock(cpu_buffer);
 	event = rb_iter_peek(iter, ts);
-	raw_spin_unlock_irqrestore(&cpu_buffer->reader_lock, flags);
+	rb_reader_unlock(cpu_buffer, dolock);
+	local_irq_restore(flags);
 
 	if (event && event->type_len == RINGBUF_TYPE_PADDING)
 		goto again;
@@ -6439,12 +6448,15 @@ void ring_buffer_iter_advance(struct ring_buffer_iter *iter)
 {
 	struct ring_buffer_per_cpu *cpu_buffer = iter->cpu_buffer;
 	unsigned long flags;
+	bool dolock;
 
-	raw_spin_lock_irqsave(&cpu_buffer->reader_lock, flags);
+	local_irq_save(flags);
+	dolock = rb_reader_lock(cpu_buffer);
 	iter->missed_events = 0;
 	rb_advance_iter(iter);
 
-	raw_spin_unlock_irqrestore(&cpu_buffer->reader_lock, flags);
+	rb_reader_unlock(cpu_buffer, dolock);
+	local_irq_restore(flags);
 }
 EXPORT_SYMBOL_GPL(ring_buffer_iter_advance);
 
-- 
2.55.0.229.g6434b31f56-goog


  parent reply	other threads:[~2026-07-21 10:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21 10:35 [PATCH v3 00/18] tracing/remotes: Add printk, dump_on_panic and boot parameters Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 01/18] tracing/remotes: Gate tracefs files opening on trace remote registration Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 02/18] tracing/remotes: Release tracefs,eventfs on registration failure Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 03/18] tracing/remotes: Use kstrtobool for boolean tracefs files Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 04/18] tracing/remotes: Use a single per-remote polling work Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 05/18] tracing/simple_ring_buffer: Add support for compressed length Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 06/18] tracing/remotes: Add dmesg tracefs file Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 07/18] tracing/remotes: selftests: Add a test for the " Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 08/18] tracing/remotes: selftests: Prefix hypervisor folder Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 09/18] ring-buffer: Use irqsave for the reader lock in ring_buffer_poll_remote Vincent Donnefort
2026-07-21 10:35 ` Vincent Donnefort [this message]
2026-07-21 10:35 ` [PATCH v3 11/18] ring-buffer: Add ring_buffer_read_remote_meta_page() Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 12/18] ring-buffer: Add kerneldoc for ring_buffer_poll_remote Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 13/18] tracing/remotes: Add dump_on_panic tracefs file Vincent Donnefort
2026-07-21 10:35 ` [PATCH v3 14/18] tracing/remotes: selftests: Add a test for the " Vincent Donnefort
2026-07-21 10:36 ` [PATCH v3 15/18] tracing/remotes: Add poll_ms " Vincent Donnefort
2026-07-21 10:36 ` [PATCH v3 16/18] tracing/remotes: Add trace_remote cmdline options Vincent Donnefort
2026-07-21 10:36 ` [PATCH v3 17/18] Documentation: tracing/remotes: Add detailed tracefs layout Vincent Donnefort
2026-07-21 10:36 ` [PATCH v3 18/18] Documentation/kernel-parameters: Add trace_remote Vincent Donnefort

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260721103603.342266-11-vdonnefort@google.com \
    --to=vdonnefort@google.com \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox