linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] tracing: ring_buffer: Rewind persistent ring buffer when reboot
Date: Wed, 28 May 2025 09:22:09 +0900	[thread overview]
Message-ID: <20250528092209.01fb26deee82e404d52a90c5@kernel.org> (raw)
In-Reply-To: <20250527094757.791e8f10@gandalf.local.home>

On Tue, 27 May 2025 09:47:57 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:

> On Tue, 27 May 2025 12:54:44 +0900
> Masami Hiramatsu (Google) <mhiramat@kernel.org> wrote:
> 
> > Here is what I meant. As far as I ran my test, it looks good (it prevents
> > over-read by `cat per_cpu/cpu0/trace_pipe_raw`)
> > 
> > diff --git a/kernel/trace/ring_buffer.c b/kernel/trace/ring_buffer.c
> > index 5034bae02f08..de1831eb3446 100644
> > --- a/kernel/trace/ring_buffer.c
> > +++ b/kernel/trace/ring_buffer.c
> > @@ -5405,6 +5405,7 @@ rb_get_reader_page(struct ring_buffer_per_cpu *cpu_buffer)
> >         unsigned long flags;
> >         int nr_loops = 0;
> >         bool ret;
> > +       u64 ts;
> >  
> >         local_irq_save(flags);
> >         arch_spin_lock(&cpu_buffer->lock);
> > @@ -5423,6 +5424,18 @@ rb_get_reader_page(struct ring_buffer_per_cpu *cpu_buffer)
> >  
> >         reader = cpu_buffer->reader_page;
> >  
> > +       /*
> > +        * Now the page->commit is not cleared when it read.
> > +        * Check whether timestamp is newer instead. We also don't
> > +        * care the head_page is overwritten. In that case, timestamp
> > +        * should be newer than reader timestamp too.
> > +        */
> > +       ts = cpu_buffer->head_page->page->time_stamp;
> > +       if (ts < reader->page->time_stamp) {
> 
> Hmm, I think this test may be too fragile. The head_page can be moved
> by the writer, and this would need to handle races.

Good point! Can we pick the page out from ring buffer as same
as reader_page? If its timestamp is newer, we push the reader
page (swap reader and head), or push back the header page.

> 
> I found an issue with commit overflow and have a couple of bugs to fix that
> touches some of this code. Let's revisit after I get those fixed.

OK, let's review it.

BTW, we need a ring buffer test tool not depending on perf tool.

Thank you,

> 
> Thanks,
> 
> -- Steve
> 
> 
> 
> > +               reader = NULL;
> > +               goto out;
> > +       }
> > +
> >         /* If there's more to read, return this page */
> >         if (cpu_buffer->reader_page->read < rb_page_size(reader))
> >                 goto out;
> > 
> 


-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

  reply	other threads:[~2025-05-28  0:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-22 15:54 [PATCH v3 0/2] tracing: Rewind persistent ring buffer Masami Hiramatsu (Google)
2025-05-22 15:54 ` [PATCH v3 1/2] tracing: ring_buffer: Rewind persistent ring buffer when reboot Masami Hiramatsu (Google)
2025-05-23 20:54   ` Steven Rostedt
2025-05-23 21:28     ` Steven Rostedt
2025-05-26  3:03       ` Masami Hiramatsu
2025-05-27  0:17         ` Masami Hiramatsu
2025-05-27  3:15           ` Masami Hiramatsu
2025-05-27  3:54             ` Masami Hiramatsu
2025-05-27 13:47               ` Steven Rostedt
2025-05-28  0:22                 ` Masami Hiramatsu [this message]
2025-05-23 23:20     ` Steven Rostedt
2025-05-26  3:44       ` Masami Hiramatsu
2025-05-27 13:48         ` Steven Rostedt
2025-06-03 16:00   ` Steven Rostedt
2025-06-03 21:58     ` Masami Hiramatsu
2025-05-22 15:54 ` [PATCH v3 2/2] tracing: Reset last-boot buffers when reading out all cpu buffers Masami Hiramatsu (Google)

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=20250528092209.01fb26deee82e404d52a90c5@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --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;
as well as URLs for NNTP newsgroup(s).