[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1504808096.13310.12.camel@tzanussi-mobl.amr.corp.intel.com>
Date: Thu, 07 Sep 2017 13:14:56 -0500
From: Tom Zanussi <tom.zanussi@...ux.intel.com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: tglx@...utronix.de, mhiramat@...nel.org, namhyung@...nel.org,
vedang.patel@...el.com, bigeasy@...utronix.de,
joel.opensrc@...il.com, joelaf@...gle.com,
mathieu.desnoyers@...icios.com, baohong.liu@...el.com,
linux-kernel@...r.kernel.org, linux-rt-users@...r.kernel.org
Subject: Re: [PATCH v2 21/40] tracing: Generalize per-element hist trigger
data
On Thu, 2017-09-07 at 13:56 -0400, Steven Rostedt wrote:
> On Tue, 5 Sep 2017 16:57:33 -0500
> Tom Zanussi <tom.zanussi@...ux.intel.com> wrote:
>
[...]
> > hist_data->map = tracing_map_create(map_bits, hist_data->key_size,
> > map_ops, hist_data);
> > @@ -1724,7 +1722,8 @@ static void hist_trigger_stacktrace_print(struct seq_file *m,
> > seq_printf(m, "%s: [%llx] %-55s", field_name,
> > uval, str);
> > } else if (key_field->flags & HIST_FIELD_FL_EXECNAME) {
> > - char *comm = elt->private_data;
> > + struct hist_elt_data *elt_data = elt->private_data;
>
> I wonder if we should have a return WARN_ON_ONCE(!elt_data); here just
> in case.
>
Yeah, that makes sense, as do the other suggestions above, will update.
Thanks,
Tom
Powered by blists - more mailing lists