aboutsummaryrefslogtreecommitdiff
path: root/block
diff options
context:
space:
mode:
authorGravatar Steven Rostedt (Google) <rostedt@goodmis.org> 2023-12-06 10:02:44 -0500
committerGravatar Steven Rostedt (Google) <rostedt@goodmis.org> 2023-12-06 15:00:59 -0500
commitb2dd797543cfa6580eac8408dd67fa02164d9e56 (patch)
tree4fbf2d2bb654312207de83937e03f51ce6c229de /block
parenttracing: Fix a possible race when disabling buffered events (diff)
downloadlinux-b2dd797543cfa6580eac8408dd67fa02164d9e56.tar.gz
linux-b2dd797543cfa6580eac8408dd67fa02164d9e56.tar.bz2
linux-b2dd797543cfa6580eac8408dd67fa02164d9e56.zip
ring-buffer: Force absolute timestamp on discard of event
There's a race where if an event is discarded from the ring buffer and an interrupt were to happen at that time and insert an event, the time stamp is still used from the discarded event as an offset. This can screw up the timings. If the event is going to be discarded, set the "before_stamp" to zero. When a new event comes in, it compares the "before_stamp" with the "write_stamp" and if they are not equal, it will insert an absolute timestamp. This will prevent the timings from getting out of sync due to the discarded event. Link: https://lore.kernel.org/linux-trace-kernel/20231206100244.5130f9b3@gandalf.local.home Cc: stable@vger.kernel.org Cc: Masami Hiramatsu <mhiramat@kernel.org> Cc: Mark Rutland <mark.rutland@arm.com> Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com> Fixes: 6f6be606e763f ("ring-buffer: Force before_stamp and write_stamp to be different on discard") Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Diffstat (limited to 'block')
0 files changed, 0 insertions, 0 deletions