ring-buffer: Update write stamp with the correct ts
authorSteven Rostedt (VMware) <rostedt@goodmis.org>
Fri, 27 Nov 2020 16:20:58 +0000 (11:20 -0500)
committerSteven Rostedt (VMware) <rostedt@goodmis.org>
Mon, 30 Nov 2020 20:21:31 +0000 (15:21 -0500)
The write stamp, used to calculate deltas between events, was updated with
the stale "ts" value in the "info" structure, and not with the updated "ts"
variable. This caused the deltas between events to be inaccurate, and when
crossing into a new sub buffer, had time go backwards.

Link: https://lkml.kernel.org/r/20201124223917.795844-1-elavila@google.com
Cc: stable@vger.kernel.org
Fixes: a389d86f7fd09 ("ring-buffer: Have nested events still record running time stamp")
Reported-by: "J. Avila" <elavila@google.com>
Tested-by: Daniel Mentz <danielmentz@google.com>
Tested-by: Will McVicker <willmcvicker@google.com>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
kernel/trace/ring_buffer.c

index dc83b3f..bccaf88 100644 (file)
@@ -3291,7 +3291,7 @@ __rb_reserve_next(struct ring_buffer_per_cpu *cpu_buffer,
                        /* Nothing came after this event between C and E */
                        info->delta = ts - info->after;
                        (void)rb_time_cmpxchg(&cpu_buffer->write_stamp,
-                                             info->after, info->ts);
+                                             info->after, ts);
                        info->ts = ts;
                } else {
                        /*