tracing: Set kernel_stack's caller size properly
authorJosef Bacik <jbacik@fb.com>
Wed, 24 Sep 2014 20:14:12 +0000 (16:14 -0400)
committerSteven Rostedt (VMware) <rostedt@goodmis.org>
Fri, 24 Jan 2020 23:09:40 +0000 (18:09 -0500)
commitcbc3b92ce037f5e7536f6db157d185cd8b8f615c
treeabec17b3175f04e667b6f5ea10b5cb11ee4a16d0
parentafccc00f75bbbee4e4ae833a96c2d29a7259c693
tracing: Set kernel_stack's caller size properly

I noticed when trying to use the trace-cmd python interface that reading the raw
buffer wasn't working for kernel_stack events.  This is because it uses a
stubbed version of __dynamic_array that doesn't do the __data_loc trick and
encode the length of the array into the field.  Instead it just shows up as a
size of 0.  So change this to __array and set the len to FTRACE_STACK_ENTRIES
since this is what we actually do in practice and matches how user_stack_trace
works.

Link: http://lkml.kernel.org/r/1411589652-1318-1-git-send-email-jbacik@fb.com
Signed-off-by: Josef Bacik <jbacik@fb.com>
[ Pulled from the archeological digging of my INBOX ]
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
kernel/trace/trace_entries.h