linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: "Jérôme Glisse" <jglisse@redhat.com>
Cc: kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 5141/5361] include/linux/hmm.h:102:22: error: field 'mmu_notifier' has incomplete type
Date: Sat, 2 Feb 2019 00:14:13 +0800	[thread overview]
Message-ID: <201902020011.aV3IBiMH%fengguang.wu@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1889 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   9fe36dd579c794ae5f1c236293c55fb6847e9654
commit: a3402cb621c1b3908600d3f364e991a6c5a8c06e [5141/5361] mm/hmm: improve driver API to work and wait over a range
config: x86_64-randconfig-b0-02012138 (attached as .config)
compiler: gcc-8 (Debian 8.2.0-14) 8.2.0
reproduce:
        git checkout a3402cb621c1b3908600d3f364e991a6c5a8c06e
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

   In file included from kernel/memremap.c:14:
>> include/linux/hmm.h:102:22: error: field 'mmu_notifier' has incomplete type
     struct mmu_notifier mmu_notifier;
                         ^~~~~~~~~~~~

vim +/mmu_notifier +102 include/linux/hmm.h

    81	
    82	
    83	/*
    84	 * struct hmm - HMM per mm struct
    85	 *
    86	 * @mm: mm struct this HMM struct is bound to
    87	 * @lock: lock protecting ranges list
    88	 * @ranges: list of range being snapshotted
    89	 * @mirrors: list of mirrors for this mm
    90	 * @mmu_notifier: mmu notifier to track updates to CPU page table
    91	 * @mirrors_sem: read/write semaphore protecting the mirrors list
    92	 * @wq: wait queue for user waiting on a range invalidation
    93	 * @notifiers: count of active mmu notifiers
    94	 * @dead: is the mm dead ?
    95	 */
    96	struct hmm {
    97		struct mm_struct	*mm;
    98		struct kref		kref;
    99		struct mutex		lock;
   100		struct list_head	ranges;
   101		struct list_head	mirrors;
 > 102		struct mmu_notifier	mmu_notifier;
   103		struct rw_semaphore	mirrors_sem;
   104		wait_queue_head_t	wq;
   105		long			notifiers;
   106		bool			dead;
   107	};
   108	

---
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: 28256 bytes --]

             reply	other threads:[~2019-02-01 16:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-01 16:14 kbuild test robot [this message]
2019-02-01 21:47 ` Andrew Morton
2019-02-01 22:04   ` Jerome Glisse
2019-02-01 22:48 ` Balbir Singh
2019-02-01 23:08   ` Jerome Glisse
2019-02-02  0:16     ` Balbir Singh

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=201902020011.aV3IBiMH%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=jglisse@redhat.com \
    --cc=kbuild-all@01.org \
    --cc=linux-mm@kvack.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