From: kbuild test robot <lkp@intel.com>
To: Jason Wang <jasowang@redhat.com>
Cc: kbuild-all@01.org, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: [vhost:linux-next 12/19] drivers/vhost/vhost.h:196:22: error: field 'mmu_notifier' has incomplete type
Date: Thu, 6 Jun 2019 07:44:04 +0800 [thread overview]
Message-ID: <201906060703.tsa7f2Ts%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1790 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git linux-next
head: aa5dc31069763f9b1afcfcf2583de258af44d72c
commit: eb43203ceabbab75b07a526b59b34bc170e0dc2c [12/19] vhost: access vq metadata through kernel virtual address
config: mips-allyesconfig (attached as .config)
compiler: mips-linux-gcc (GCC) 7.4.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 eb43203ceabbab75b07a526b59b34bc170e0dc2c
# save the attached .config to linux build tree
GCC_VERSION=7.4.0 make.cross ARCH=mips
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from drivers/vhost/net.c:37:0:
>> drivers/vhost/vhost.h:196:22: error: field 'mmu_notifier' has incomplete type
struct mmu_notifier mmu_notifier;
^~~~~~~~~~~~
vim +/mmu_notifier +196 drivers/vhost/vhost.h
193
194 struct vhost_dev {
195 struct mm_struct *mm;
> 196 struct mmu_notifier mmu_notifier;
197 struct mutex mutex;
198 struct vhost_virtqueue **vqs;
199 int nvqs;
200 struct eventfd_ctx *log_ctx;
201 struct llist_head work_list;
202 struct task_struct *worker;
203 struct vhost_umem *umem;
204 struct vhost_umem *iotlb;
205 spinlock_t iotlb_lock;
206 struct list_head read_list;
207 struct list_head pending_list;
208 wait_queue_head_t wait;
209 int iov_limit;
210 int weight;
211 int byte_weight;
212 };
213
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 61147 bytes --]
reply other threads:[~2019-06-05 23:44 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=201906060703.tsa7f2Ts%lkp@intel.com \
--to=lkp@intel.com \
--cc=jasowang@redhat.com \
--cc=kbuild-all@01.org \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).