Thread (4 messages) 4 messages, 2 authors, 2026-01-31

Re: [PATCH] tracing: Fix duration calculation bug (rettime - calltime) on ARM architecture

From: Steven Rostedt <rostedt@goodmis.org>
Date: 2026-01-31 12:56:15
Also in: lkml

On Sat, 31 Jan 2026 18:08:41 +0800 (CST)
"jempty.liang" [off-list ref] wrote:
quoted
How is this unique to arm? I'm not able to duplicate this on x86, but the
code here is all generic code. What's different?
   
You're right, this bug is only reproducible on ARM.  
You didn't answer my question. I understand that you said this only
impacts ARM. I'm asking you why does it only impact ARM? There's
nothing in this patch that is ARM specific? What is different about ARM
that makes this code have an issue where it doesn't have an issue with
x86?
  
quoted
You show what the wrong output is and the correct output, but you
don't mention what was the bug and how this fixes it. From the
change log, it looks like you just tried something and it worked,
but do not know why it worked.

I'd like to know what the bug was and how this fixes it. It's not
obvious.
   
Before the patch, do_open_execat had an abnormal execution duration
of 2757369004 us (over 1 second); the patch resolves this and
restores the function to a normal duration range.  
You still haven't answered my question. You are just telling me that
the patch fixes it but you do not tell me what in the code was wrong
and why the patch fixes it!

-- Steve
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help