From: Steven Rostedt <rostedt@goodmis.org>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: linux-trace-kernel@vger.kernel.org
Subject: Re: [bug report] tracing: Have persistent ring buffer print syscalls normally
Date: Fri, 31 Oct 2025 08:35:05 -0400 [thread overview]
Message-ID: <20251031083505.477ca703@gandalf.local.home> (raw)
In-Reply-To: <aQRLBV_KzDHaaYiG@stanley.mountain>
On Fri, 31 Oct 2025 08:37:09 +0300
Dan Carpenter <dan.carpenter@linaro.org> wrote:
> 4271 if ((tr->text_delta)) {
> 4272 /* ftrace and system call events are still OK */
> --> 4273 if ((event->type > __TRACE_LAST_TYPE) &&
> 4274 !is_syscall_event(event))
>
> I feel like there was a line of code here that was accidentally left out
> of the commit.
Or one was added ;-)
>
> 4275 return print_event_fields(iter, event);
>
> Or we could add another tab here, but my guess is there is a missing
> statement.
The commit that caused this had:
@@ -4251,10 +4268,12 @@ static enum print_line_t print_trace_fmt(struct trace_iterator *iter)
* safe to use if the array has delta offsets
* Force printing via the fields.
*/
- if ((tr->text_delta) &&
- event->type > __TRACE_LAST_TYPE)
+ if ((tr->text_delta)) {
+ /* ftrace and system call events are still OK */
+ if ((event->type > __TRACE_LAST_TYPE) &&
+ !is_syscall_event(event))
return print_event_fields(iter, event);
-
+ }
return event->funcs->trace(iter, sym_flags, event);
}
I broke the original if statement into two if statements so that it would
look better when I added another conditional. I just forgot to increase the
indentation of the if block.
Thus, a new tab is needed.
Thanks,
-- Steve
prev parent reply other threads:[~2025-10-31 12:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 5:37 [bug report] tracing: Have persistent ring buffer print syscalls normally Dan Carpenter
2025-10-31 12:35 ` Steven Rostedt [this message]
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=20251031083505.477ca703@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=dan.carpenter@linaro.org \
--cc=linux-trace-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.