From: kbuild test robot <lkp@intel.com>
To: Alexei Starovoitov <ast@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
"Steven Rostedt (VMware)" <rostedt@goodmis.org>
Subject: kernel//trace/fgraph.c:111:35: error: 'MCOUNT_INSN_SIZE' undeclared; did you mean 'UCOUNT_COUNTS'?
Date: Thu, 2 Jan 2020 02:09:22 +0800 [thread overview]
Message-ID: <202001020219.zvE3vsty%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2605 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 738d2902773e30939a982c8df7a7f94293659810
commit: ff205766dbbee024a4a716638868d98ffb17748a ftrace: Fix function_graph tracer interaction with BPF trampoline
date: 3 weeks ago
config: riscv-randconfig-a001-20200102 (attached as .config)
compiler: riscv64-linux-gcc (GCC) 7.5.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout ff205766dbbee024a4a716638868d98ffb17748a
# save the attached .config to linux build tree
GCC_VERSION=7.5.0 make.cross ARCH=riscv
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
kernel//trace/fgraph.c: In function 'function_graph_enter':
>> kernel//trace/fgraph.c:111:35: error: 'MCOUNT_INSN_SIZE' undeclared (first use in this function); did you mean 'UCOUNT_COUNTS'?
ftrace_find_rec_direct(ret - MCOUNT_INSN_SIZE))
^~~~~~~~~~~~~~~~
UCOUNT_COUNTS
kernel//trace/fgraph.c:111:35: note: each undeclared identifier is reported only once for each function it appears in
vim +111 kernel//trace/fgraph.c
98
99 int function_graph_enter(unsigned long ret, unsigned long func,
100 unsigned long frame_pointer, unsigned long *retp)
101 {
102 struct ftrace_graph_ent trace;
103
104 /*
105 * Skip graph tracing if the return location is served by direct trampoline,
106 * since call sequence and return addresses is unpredicatable anymore.
107 * Ex: BPF trampoline may call original function and may skip frame
108 * depending on type of BPF programs attached.
109 */
110 if (ftrace_direct_func_count &&
> 111 ftrace_find_rec_direct(ret - MCOUNT_INSN_SIZE))
112 return -EBUSY;
113 trace.func = func;
114 trace.depth = ++current->curr_ret_depth;
115
116 if (ftrace_push_return_trace(ret, func, frame_pointer, retp))
117 goto out;
118
119 /* Only trace if the calling function expects to */
120 if (!ftrace_graph_entry(&trace))
121 goto out_ret;
122
123 return 0;
124 out_ret:
125 current->curr_ret_stack--;
126 out:
127 current->curr_ret_depth--;
128 return -EBUSY;
129 }
130
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 24697 bytes --]
next reply other threads:[~2020-01-01 18:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-01 18:09 kbuild test robot [this message]
2020-01-03 3:07 ` kernel//trace/fgraph.c:111:35: error: 'MCOUNT_INSN_SIZE' undeclared; did you mean 'UCOUNT_COUNTS'? Steven Rostedt
2020-01-03 3:09 ` [PATCH] tracing: Define MCOUNT_INSN_SIZE when not defined without direct calls Steven Rostedt
2020-01-03 3:09 ` [PATCH] tracing: Have stack tracer compile when MCOUNT_INSN_SIZE is not defined Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202001020219.zvE3vsty%lkp@intel.com \
--to=lkp@intel.com \
--cc=ast@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox