[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230816111142.1b774383@gandalf.local.home>
Date: Wed, 16 Aug 2023 11:11:42 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Sven Schnelle <svens@...ux.ibm.com>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 0/3] few fixes for synthetic trace events
On Wed, 16 Aug 2023 11:08:52 +0200
Sven Schnelle <svens@...ux.ibm.com> wrote:
> Sven Schnelle <svens@...ux.ibm.com> writes:
>
> > Hi Steven,
> >
> > I'm now sending these patches in one patchset, because the second patch
> > has a dependeny on the union vs. cast fix.
> >
> > Changes in v3:
> > - remove superfluous struct around union trace_synth_field
> >
> > Changes in v2:
> > - cosmetic changes
> > - add struct trace_dynamic_info to include/linux/trace_events.h
> >
> > Sven Schnelle (3):
> > tracing/synthetic: use union instead of casts
> > tracing/synthetic: skip first entry for stack traces
> > tracing/synthetic: allocate one additional element for size
> >
> > include/linux/trace_events.h | 11 ++++
> > kernel/trace/trace.h | 8 +++
> > kernel/trace/trace_events_synth.c | 103 ++++++++++++------------------
> > 3 files changed, 60 insertions(+), 62 deletions(-)
>
> Gentle ping? We're still seeing a lot of KASAN warnings.
Can you resend and include a Cc to linux-trace-kernel@...r.kernel.org. That
will put it into patchwork:
https://patchwork.kernel.org/project/linux-trace-kernel/list/
Also, include everyone in the MAINTAINERS file too please.
That's what I use to know what to pull in for tracing. I have a personal
patchwork on my INBOX that this did go into, but that's always considered
lower priority.
-- Steve
Powered by blists - more mailing lists