linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Souptick Joarder <jrdr.linux@gmail.com>
Cc: kbuild-all@01.org, akpm@linux-foundation.org, rppt@linux.ibm.com,
	mhocko@suse.com, dan.j.williams@intel.com, willy@infradead.org,
	kirill.shutemov@linux.intel.com, vbabka@suse.cz, riel@redhat.com,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	william.kucharski@oracle.com
Subject: Re: [PATCH v4] mm: Create the new vm_fault_t type
Date: Wed, 9 Jan 2019 23:13:42 +0800	[thread overview]
Message-ID: <201901092347.nIGS7dtC%fengguang.wu@intel.com> (raw)
In-Reply-To: <20190108183041.GA12137@jordon-HP-15-Notebook-PC>

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

Hi Souptick,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on linus/master]
[also build test WARNING on v5.0-rc1 next-20190109]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Souptick-Joarder/mm-Create-the-new-vm_fault_t-type/20190109-154216
config: x86_64-allmodconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All warnings (new ones prefixed by >>):

>> kernel/memremap.c:46:34: warning: incorrect type in return expression (different base types)
   kernel/memremap.c:46:34:    expected restricted vm_fault_t
   kernel/memremap.c:46:34:    got int

vim +46 kernel/memremap.c

9476df7d Dan Williams     2016-01-15  19  
5042db43 J�r�me Glisse    2017-09-08  20  #if IS_ENABLED(CONFIG_DEVICE_PRIVATE)
2b740303 Souptick Joarder 2018-08-23  21  vm_fault_t device_private_entry_fault(struct vm_area_struct *vma,
5042db43 J�r�me Glisse    2017-09-08  22  		       unsigned long addr,
5042db43 J�r�me Glisse    2017-09-08  23  		       swp_entry_t entry,
5042db43 J�r�me Glisse    2017-09-08  24  		       unsigned int flags,
5042db43 J�r�me Glisse    2017-09-08  25  		       pmd_t *pmdp)
5042db43 J�r�me Glisse    2017-09-08  26  {
5042db43 J�r�me Glisse    2017-09-08  27  	struct page *page = device_private_entry_to_page(entry);
063a7d1d Dan Williams     2018-12-28  28  	struct hmm_devmem *devmem;
063a7d1d Dan Williams     2018-12-28  29  
063a7d1d Dan Williams     2018-12-28  30  	devmem = container_of(page->pgmap, typeof(*devmem), pagemap);
5042db43 J�r�me Glisse    2017-09-08  31  
5042db43 J�r�me Glisse    2017-09-08  32  	/*
5042db43 J�r�me Glisse    2017-09-08  33  	 * The page_fault() callback must migrate page back to system memory
5042db43 J�r�me Glisse    2017-09-08  34  	 * so that CPU can access it. This might fail for various reasons
5042db43 J�r�me Glisse    2017-09-08  35  	 * (device issue, device was unsafely unplugged, ...). When such
5042db43 J�r�me Glisse    2017-09-08  36  	 * error conditions happen, the callback must return VM_FAULT_SIGBUS.
5042db43 J�r�me Glisse    2017-09-08  37  	 *
5042db43 J�r�me Glisse    2017-09-08  38  	 * Note that because memory cgroup charges are accounted to the device
5042db43 J�r�me Glisse    2017-09-08  39  	 * memory, this should never fail because of memory restrictions (but
5042db43 J�r�me Glisse    2017-09-08  40  	 * allocation of regular system page might still fail because we are
5042db43 J�r�me Glisse    2017-09-08  41  	 * out of memory).
5042db43 J�r�me Glisse    2017-09-08  42  	 *
5042db43 J�r�me Glisse    2017-09-08  43  	 * There is a more in-depth description of what that callback can and
5042db43 J�r�me Glisse    2017-09-08  44  	 * cannot do, in include/linux/memremap.h
5042db43 J�r�me Glisse    2017-09-08  45  	 */
063a7d1d Dan Williams     2018-12-28 @46  	return devmem->page_fault(vma, addr, page, flags, pmdp);
5042db43 J�r�me Glisse    2017-09-08  47  }
5042db43 J�r�me Glisse    2017-09-08  48  EXPORT_SYMBOL(device_private_entry_fault);
5042db43 J�r�me Glisse    2017-09-08  49  #endif /* CONFIG_DEVICE_PRIVATE */
5042db43 J�r�me Glisse    2017-09-08  50  

:::::: The code at line 46 was first introduced by commit
:::::: 063a7d1d3623db31ca5d2309cab6030ebf93b72f mm/hmm: fix memremap.h, move dev_page_fault_t callback to hmm

:::::: TO: Dan Williams <dan.j.williams@intel.com>
:::::: CC: Linus Torvalds <torvalds@linux-foundation.org>

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

WARNING: multiple messages have this Message-ID
From: kbuild test robot <lkp@intel.com>
To: Souptick Joarder <jrdr.linux@gmail.com>
Cc: kbuild-all@01.org, akpm@linux-foundation.org, rppt@linux.ibm.com,
	mhocko@suse.com, dan.j.williams@intel.com, willy@infradead.org,
	kirill.shutemov@linux.intel.com, vbabka@suse.cz, riel@redhat.com,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	william.kucharski@oracle.com
Subject: Re: [PATCH v4] mm: Create the new vm_fault_t type
Date: Wed, 9 Jan 2019 23:13:42 +0800	[thread overview]
Message-ID: <201901092347.nIGS7dtC%fengguang.wu@intel.com> (raw)
Message-ID: <20190109151342.AtXx28zkLvp53M_ZrFaEUDn7W6JdVCrCzI5UxIyZII8@z> (raw)
In-Reply-To: <20190108183041.GA12137@jordon-HP-15-Notebook-PC>

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

Hi Souptick,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on linus/master]
[also build test WARNING on v5.0-rc1 next-20190109]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Souptick-Joarder/mm-Create-the-new-vm_fault_t-type/20190109-154216
config: x86_64-allmodconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All warnings (new ones prefixed by >>):

>> kernel/memremap.c:46:34: warning: incorrect type in return expression (different base types)
   kernel/memremap.c:46:34:    expected restricted vm_fault_t
   kernel/memremap.c:46:34:    got int

vim +46 kernel/memremap.c

9476df7d Dan Williams     2016-01-15  19  
5042db43 Jérôme Glisse    2017-09-08  20  #if IS_ENABLED(CONFIG_DEVICE_PRIVATE)
2b740303 Souptick Joarder 2018-08-23  21  vm_fault_t device_private_entry_fault(struct vm_area_struct *vma,
5042db43 Jérôme Glisse    2017-09-08  22  		       unsigned long addr,
5042db43 Jérôme Glisse    2017-09-08  23  		       swp_entry_t entry,
5042db43 Jérôme Glisse    2017-09-08  24  		       unsigned int flags,
5042db43 Jérôme Glisse    2017-09-08  25  		       pmd_t *pmdp)
5042db43 Jérôme Glisse    2017-09-08  26  {
5042db43 Jérôme Glisse    2017-09-08  27  	struct page *page = device_private_entry_to_page(entry);
063a7d1d Dan Williams     2018-12-28  28  	struct hmm_devmem *devmem;
063a7d1d Dan Williams     2018-12-28  29  
063a7d1d Dan Williams     2018-12-28  30  	devmem = container_of(page->pgmap, typeof(*devmem), pagemap);
5042db43 Jérôme Glisse    2017-09-08  31  
5042db43 Jérôme Glisse    2017-09-08  32  	/*
5042db43 Jérôme Glisse    2017-09-08  33  	 * The page_fault() callback must migrate page back to system memory
5042db43 Jérôme Glisse    2017-09-08  34  	 * so that CPU can access it. This might fail for various reasons
5042db43 Jérôme Glisse    2017-09-08  35  	 * (device issue, device was unsafely unplugged, ...). When such
5042db43 Jérôme Glisse    2017-09-08  36  	 * error conditions happen, the callback must return VM_FAULT_SIGBUS.
5042db43 Jérôme Glisse    2017-09-08  37  	 *
5042db43 Jérôme Glisse    2017-09-08  38  	 * Note that because memory cgroup charges are accounted to the device
5042db43 Jérôme Glisse    2017-09-08  39  	 * memory, this should never fail because of memory restrictions (but
5042db43 Jérôme Glisse    2017-09-08  40  	 * allocation of regular system page might still fail because we are
5042db43 Jérôme Glisse    2017-09-08  41  	 * out of memory).
5042db43 Jérôme Glisse    2017-09-08  42  	 *
5042db43 Jérôme Glisse    2017-09-08  43  	 * There is a more in-depth description of what that callback can and
5042db43 Jérôme Glisse    2017-09-08  44  	 * cannot do, in include/linux/memremap.h
5042db43 Jérôme Glisse    2017-09-08  45  	 */
063a7d1d Dan Williams     2018-12-28 @46  	return devmem->page_fault(vma, addr, page, flags, pmdp);
5042db43 Jérôme Glisse    2017-09-08  47  }
5042db43 Jérôme Glisse    2017-09-08  48  EXPORT_SYMBOL(device_private_entry_fault);
5042db43 Jérôme Glisse    2017-09-08  49  #endif /* CONFIG_DEVICE_PRIVATE */
5042db43 Jérôme Glisse    2017-09-08  50  

:::::: The code at line 46 was first introduced by commit
:::::: 063a7d1d3623db31ca5d2309cab6030ebf93b72f mm/hmm: fix memremap.h, move dev_page_fault_t callback to hmm

:::::: TO: Dan Williams <dan.j.williams@intel.com>
:::::: CC: Linus Torvalds <torvalds@linux-foundation.org>

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

  parent reply	other threads:[~2019-01-09 15:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-08 18:30 Souptick Joarder
2019-01-08 18:29 ` Matthew Wilcox
2019-01-09 11:50 ` kbuild test robot
2019-01-09 15:13 ` kbuild test robot [this message]
2019-01-09 15:13   ` kbuild test robot

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=201901092347.nIGS7dtC%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=dan.j.williams@intel.com \
    --cc=jrdr.linux@gmail.com \
    --cc=kbuild-all@01.org \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=riel@redhat.com \
    --cc=rppt@linux.ibm.com \
    --cc=vbabka@suse.cz \
    --cc=william.kucharski@oracle.com \
    --cc=willy@infradead.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