From: Chunfeng Yun <chunfeng.yun@mediatek.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
<linux-usb@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [for-next][PATCH 13/23] USB: mtu3: tracing: Use the new __vstring() helper
Date: Tue, 19 Jul 2022 13:18:54 +0800 [thread overview]
Message-ID: <27fb716259fc88cba955691c246a6bdaf31b38d8.camel@mediatek.com> (raw)
In-Reply-To: <20220715172423.6b57b9eb@gandalf.local.home>
On Fri, 2022-07-15 at 17:24 -0400, Steven Rostedt wrote:
> On Fri, 15 Jul 2022 18:01:44 +0800
> Chunfeng Yun <chunfeng.yun@mediatek.com> wrote:
>
> > irq/254-1120100-137 [000] d..1. 266.629662: mtu3_log:
> > 11201000.usb: ep0_state SETUPr-speed
> >
> > "r-speed" seems the remain of last log;
>
> I found an off-by-one bug in the vstring patch. I'll rebase, test and
> try
> again.
>
> In the mean time, care to add this on top to make sure it's fixed?
>
> Thanks!
>
> -- Steve
>
> diff --git a/include/linux/trace_events.h
> b/include/linux/trace_events.h
> index e6f8ba52a958..b18759a673c6 100644
> --- a/include/linux/trace_events.h
> +++ b/include/linux/trace_events.h
> @@ -922,16 +922,16 @@ perf_trace_buf_submit(void *raw_data, int size,
> int rctx, u16 type,
> * gcc warns that you can not use a va_list in an inlined
> * function. But lets me make it into a macro :-/
> */
> -#define __trace_event_vstr_len(fmt, va) \
> -({ \
> - va_list __ap; \
> - int __ret; \
> - \
> - va_copy(__ap, *(va)); \
> - __ret = vsnprintf(NULL, 0, fmt, __ap); \
> - va_end(__ap); \
> - \
> - min(__ret, TRACE_EVENT_STR_MAX); \
> +#define __trace_event_vstr_len(fmt, va) \
> +({ \
> + va_list __ap; \
> + int __ret; \
> + \
> + va_copy(__ap, *(va)); \
> + __ret = vsnprintf(NULL, 0, fmt, __ap) + 1; \
It works fine now, thanks a lot
> + va_end(__ap); \
> + \
> + min(__ret, TRACE_EVENT_STR_MAX); \
> })
>
> #endif /* _LINUX_TRACE_EVENT_H */
prev parent reply other threads:[~2022-07-19 6:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220714164256.403842845@goodmis.org>
2022-07-14 16:43 ` [for-next][PATCH 13/23] USB: mtu3: tracing: Use the new __vstring() helper Steven Rostedt
2022-07-15 6:32 ` Chunfeng Yun
2022-07-15 21:39 ` Steven Rostedt
2022-07-19 5:23 ` Chunfeng Yun
2022-07-19 15:24 ` Steven Rostedt
2022-07-15 10:01 ` Chunfeng Yun
2022-07-15 14:36 ` Steven Rostedt
2022-07-15 21:24 ` Steven Rostedt
2022-07-19 5:18 ` Chunfeng Yun [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=27fb716259fc88cba955691c246a6bdaf31b38d8.camel@mediatek.com \
--to=chunfeng.yun@mediatek.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox