summaryrefslogtreecommitdiffstats
path: root/samples
diff options
context:
space:
mode:
authorAndrea Righi <andrea.righi@canonical.com>2020-11-28 10:15:17 +0100
committerSteven Rostedt (VMware) <rostedt@goodmis.org>2020-11-30 21:22:05 +0100
commit8785f51a17083eee7c37606079c6447afc6ba102 (patch)
tree27ebc928988e9b52f7311697260affe50052ea93 /samples
parentring-buffer: Update write stamp with the correct ts (diff)
downloadlinux-8785f51a17083eee7c37606079c6447afc6ba102.tar.xz
linux-8785f51a17083eee7c37606079c6447afc6ba102.zip
ring-buffer: Set the right timestamp in the slow path of __rb_reserve_next()
In the slow path of __rb_reserve_next() a nested event(s) can happen between evaluating the timestamp delta of the current event and updating write_stamp via local_cmpxchg(); in this case the delta is not valid anymore and it should be set to 0 (same timestamp as the interrupting event), since the event that we are currently processing is not the last event in the buffer. Link: https://lkml.kernel.org/r/X8IVJcp1gRE+FJCJ@xps-13-7390 Cc: Ingo Molnar <mingo@redhat.com> Cc: Masami Hiramatsu <mhiramat@kernel.org> Cc: stable@vger.kernel.org Link: https://lwn.net/Articles/831207 Fixes: a389d86f7fd0 ("ring-buffer: Have nested events still record running time stamp") Signed-off-by: Andrea Righi <andrea.righi@canonical.com> Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'samples')
0 files changed, 0 insertions, 0 deletions