Re: TP_printk() bug with %c, and more?

2024-04-15 Thread Steven Rostedt
On Tue, 16 Apr 2024 04:08:46 +0200 Luca Ceresoli wrote: > Thanks for the insight. I'm definitely trying to fix this based on your > hint as soon as I get my hand on a board. I have a patch I forgot to send out. Let me do that now. -- Steve

Re: TP_printk() bug with %c, and more?

2024-04-15 Thread Luca Ceresoli
Hello Steven, On Mon, 15 Apr 2024 04:44:30 -0400 Steven Rostedt wrote: > On Mon, 18 Mar 2024 16:43:07 +0100 > Luca Ceresoli wrote: > > > However the arrows are still reversed. > > This requires a kernel change. The problem is that the print fmt has: > > print fmt: "%c%s %s %s %s %s",

Re: TP_printk() bug with %c, and more?

2024-04-15 Thread Steven Rostedt
On Mon, 18 Mar 2024 16:43:07 +0100 Luca Ceresoli wrote: > However the arrows are still reversed. This requires a kernel change. The problem is that the print fmt has: print fmt: "%c%s %s %s %s %s", (int) REC->path_node && (int) REC->path_connect ? '*' : ' ', __get_str(wname),

Re: TP_printk() bug with %c, and more?

2024-03-18 Thread Steven Rostedt
On Mon, 18 Mar 2024 16:43:07 +0100 Luca Ceresoli wrote: > Indeed I was on an older version, apologies. > > I upgraded both libtraceevent and trace-cmd to master and applied your > patch, now the %c is formatted correctly. > > However the arrows are still reversed. > > Is this what you were

Re: TP_printk() bug with %c, and more?

2024-03-18 Thread Luca Ceresoli
Hello Steven, On Fri, 15 Mar 2024 14:58:52 -0400 Steven Rostedt wrote: > On Fri, 15 Mar 2024 19:03:12 +0100 > Luca Ceresoli wrote: > > > > > > > > > I've come across an unexpected behaviour in the kernel tracing > > > > infrastructure that looks like a bug, or maybe two. > > > > > > > >

Re: TP_printk() bug with %c, and more?

2024-03-15 Thread Steven Rostedt
On Fri, 15 Mar 2024 19:03:12 +0100 Luca Ceresoli wrote: > > > > > > I've come across an unexpected behaviour in the kernel tracing > > > infrastructure that looks like a bug, or maybe two. > > > > > > Cc-ing ASoC maintainers for as it appeared using ASoC traces, but it > > > does not look

Re: TP_printk() bug with %c, and more?

2024-03-15 Thread Luca Ceresoli
Hello Steven, thanks for the quick feedback! On Fri, 15 Mar 2024 13:21:46 -0400 Steven Rostedt wrote: > On Fri, 15 Mar 2024 17:49:00 +0100 > Luca Ceresoli wrote: > > > Hello Linux tracing maintainers, > > Hi Luca! > > > > > I've come across an unexpected behaviour in the kernel tracing

Re: TP_printk() bug with %c, and more?

2024-03-15 Thread Steven Rostedt
On Fri, 15 Mar 2024 17:49:00 +0100 Luca Ceresoli wrote: > Hello Linux tracing maintainers, Hi Luca! > > I've come across an unexpected behaviour in the kernel tracing > infrastructure that looks like a bug, or maybe two. > > Cc-ing ASoC maintainers for as it appeared using ASoC traces, but

TP_printk() bug with %c, and more?

2024-03-15 Thread Luca Ceresoli
Hello Linux tracing maintainers, I've come across an unexpected behaviour in the kernel tracing infrastructure that looks like a bug, or maybe two. Cc-ing ASoC maintainers for as it appeared using ASoC traces, but it does not look ASoC-specific. It all started when using this trace-cmd sequence