From: kernel test robot <lkp@intel.com>
To: Jiri Olsa <jolsa@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [jolsa-perf:bpf/tracing_multi_new_1 22/23] kernel/bpf/syscall.c:3150:27: error: field 'fops' has incomplete type
Date: Sat, 13 Aug 2022 22:29:17 +0800 [thread overview]
Message-ID: <202208132235.CyiLD4fT-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git bpf/tracing_multi_new_1
head: e27bb6c0f6805082ef71568985f74dcefe7ff6ff
commit: dc38a65ab46f4ba538353c1eb7c64ac36202eb54 [22/23] fix
config: i386-randconfig-a003 (https://download.01.org/0day-ci/archive/20220813/202208132235.CyiLD4fT-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git/commit/?id=dc38a65ab46f4ba538353c1eb7c64ac36202eb54
git remote add jolsa-perf https://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git
git fetch --no-tags jolsa-perf bpf/tracing_multi_new_1
git checkout dc38a65ab46f4ba538353c1eb7c64ac36202eb54
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> kernel/bpf/syscall.c:3150:27: error: field 'fops' has incomplete type
3150 | struct ftrace_ops fops;
| ^~~~
vim +/fops +3150 kernel/bpf/syscall.c
3144
3145 struct bpf_tracing_multi_link {
3146 struct bpf_link link;
3147 enum bpf_attach_type attach_type;
3148 struct bpf_tramp_prog tp;
3149 struct bpf_tramp_id *id;
> 3150 struct ftrace_ops fops;
3151 };
3152
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-08-13 14:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202208132235.CyiLD4fT-lkp@intel.com \
--to=lkp@intel.com \
--cc=jolsa@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.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