Re: [RFC PATCH v4 1/3] tracing/events: Fix wrong sample output by storing array length instead of size

From: Sara Rostedt <sara@rostedt.homelinux.com>
To: He Kuang <hekuang@huawei.com>, Javi Merino <javi.merino@arm.com>
Cc: ast@plumgrid.com, masami.hiramatsu.pt@hitachi.com,
	acme@kernel.org, a.p.zijlstra@chello.nl, mingo@redhat.com,
	namhyung@kernel.org, jolsa@kernel.org, wangnan0@huawei.com,
	pi3orama@163.com, linux-kernel@vger.kernel.org,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Dave Martin" <Dave.Martin@arm.com>
Subject: Re: [RFC PATCH v4 1/3] tracing/events: Fix wrong sample output by storing array length instead of size
Date: Fri, 17 Jul 2015 13:24:39 -0400	[thread overview]
Message-ID: <20150717132439.689f8cc8@gandalf.local.home> (raw)
In-Reply-To: <20150717103215.7d285953@gandalf.local.home>

On Fri, 17 Jul 2015 10:32:15 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:

> > @@ -453,7 +454,7 @@ trace_event_define_fields_##call(struct trace_event_call *event_call)	\
> >  	__item_length = (len) * sizeof(type);				\
> >  	__data_offsets->item = __data_size +				\
> >  			       offsetof(typeof(*entry), __data);	\
> > -	__data_offsets->item |= __item_length << 16;			\
> > +	__data_offsets->item |= (len) << 16;				\
> 
> This change affects all callers of dymanic_array, not just bitmasks.

This also affects what goes into the trace record and changes what
tools expect. That size is to be the size of the entire allocated
space, not the size of an individual element or the number of them.

> 
> >  	__data_size += __item_length;
> >  
> >  #undef __string
> 
> BTW, if I revert commit ac01ce1410fc2 "tracing: Make
> ftrace_print_array_seq compute buf_len" it works again.
> 
> I'm going to look into this some more, and maybe the answer is to go
> back and just pass in buffer length here. I can't see what was broken
> before that change.

I'm thinking the best thing to do is to revert that patch and make the
second argument of __print_array() the size and not the count.

-- Steve