linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Joao Martins <joao.m.martins@oracle.com>, linux-mm@kvack.org
Cc: kbuild-all@lists.01.org, Dan Williams <dan.j.williams@intel.com>,
	Vishal Verma <vishal.l.verma@intel.com>,
	Dave Jiang <dave.jiang@intel.com>,
	Naoya Horiguchi <naoya.horiguchi@nec.com>,
	Matthew Wilcox <willy@infradead.org>,
	Jason Gunthorpe <jgg@ziepe.ca>,
	John Hubbard <jhubbard@nvidia.com>,
	Jane Chu <jane.chu@oracle.com>,
	Muchun Song <songmuchun@bytedance.com>
Subject: Re: [PATCH v7 10/11] device-dax: remove pfn from __dev_dax_{pte,pmd,pud}_fault()
Date: Fri, 3 Dec 2021 15:30:49 +0800	[thread overview]
Message-ID: <202112031508.uJvmXK7U-lkp@intel.com> (raw)
In-Reply-To: <20211202204422.26777-11-joao.m.martins@oracle.com>

Hi Joao,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on hnaz-mm/master]

url:    https://github.com/0day-ci/linux/commits/Joao-Martins/mm-device-dax-Introduce-compound-pages-in-devmap/20211203-044722
base:   https://github.com/hnaz/linux-mm master
config: i386-randconfig-a013-20211202 (https://download.01.org/0day-ci/archive/20211203/202112031508.uJvmXK7U-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
        # https://github.com/0day-ci/linux/commit/ca6ce8fa76f139a8d4021fc95ce7ba1ebb7a06e2
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Joao-Martins/mm-device-dax-Introduce-compound-pages-in-devmap/20211203-044722
        git checkout ca6ce8fa76f139a8d4021fc95ce7ba1ebb7a06e2
        # save the config file to linux build tree
        mkdir build_dir
        make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash drivers/

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   drivers/dax/device.c: In function 'dev_dax_huge_fault':
>> drivers/dax/device.c:246:8: error: too few arguments to function '__dev_dax_pud_fault'
     246 |   rc = __dev_dax_pud_fault(dev_dax, vmf);
         |        ^~~~~~~~~~~~~~~~~~~
   drivers/dax/device.c:218:19: note: declared here
     218 | static vm_fault_t __dev_dax_pud_fault(struct dev_dax *dev_dax,
         |                   ^~~~~~~~~~~~~~~~~~~
   drivers/dax/device.c: At top level:
   drivers/dax/device.c:394:5: warning: no previous prototype for 'dev_dax_probe' [-Wmissing-prototypes]
     394 | int dev_dax_probe(struct dev_dax *dev_dax)
         |     ^~~~~~~~~~~~~


vim +/__dev_dax_pud_fault +246 drivers/dax/device.c

   224	
   225	static vm_fault_t dev_dax_huge_fault(struct vm_fault *vmf,
   226			enum page_entry_size pe_size)
   227	{
   228		struct file *filp = vmf->vma->vm_file;
   229		vm_fault_t rc = VM_FAULT_SIGBUS;
   230		int id;
   231		struct dev_dax *dev_dax = filp->private_data;
   232	
   233		dev_dbg(&dev_dax->dev, "%s: %s (%#lx - %#lx) size = %d\n", current->comm,
   234				(vmf->flags & FAULT_FLAG_WRITE) ? "write" : "read",
   235				vmf->vma->vm_start, vmf->vma->vm_end, pe_size);
   236	
   237		id = dax_read_lock();
   238		switch (pe_size) {
   239		case PE_SIZE_PTE:
   240			rc = __dev_dax_pte_fault(dev_dax, vmf);
   241			break;
   242		case PE_SIZE_PMD:
   243			rc = __dev_dax_pmd_fault(dev_dax, vmf);
   244			break;
   245		case PE_SIZE_PUD:
 > 246			rc = __dev_dax_pud_fault(dev_dax, vmf);
   247			break;
   248		default:
   249			rc = VM_FAULT_SIGBUS;
   250		}
   251	
   252		dax_read_unlock(id);
   253	
   254		return rc;
   255	}
   256	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org


  reply	other threads:[~2021-12-03  7:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-02 20:44 [PATCH v7 00/11] mm, device-dax: Introduce compound pages in devmap Joao Martins
2021-12-02 20:44 ` [PATCH v7 01/11] memory-failure: fetch compound_head after pgmap_pfn_valid() Joao Martins
2021-12-02 20:44 ` [PATCH v7 02/11] mm/page_alloc: split prep_compound_page into head and tail subparts Joao Martins
2021-12-02 20:44 ` [PATCH v7 03/11] mm/page_alloc: refactor memmap_init_zone_device() page init Joao Martins
2021-12-02 20:44 ` [PATCH v7 04/11] mm/memremap: add ZONE_DEVICE support for compound pages Joao Martins
2021-12-02 20:44 ` [PATCH v7 05/11] device-dax: use ALIGN() for determining pgoff Joao Martins
2021-12-02 20:44 ` [PATCH v7 06/11] device-dax: use struct_size() Joao Martins
2021-12-02 20:44 ` [PATCH v7 07/11] device-dax: ensure dev_dax->pgmap is valid for dynamic devices Joao Martins
2021-12-02 20:44 ` [PATCH v7 08/11] device-dax: factor out page mapping initialization Joao Martins
2021-12-02 20:44 ` [PATCH v7 09/11] device-dax: set mapping prior to vmf_insert_pfn{,_pmd,pud}() Joao Martins
2021-12-02 20:44 ` [PATCH v7 10/11] device-dax: remove pfn from __dev_dax_{pte,pmd,pud}_fault() Joao Martins
2021-12-03  7:30   ` kernel test robot [this message]
2021-12-02 20:44 ` [PATCH v7 11/11] device-dax: compound devmap support Joao Martins

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=202112031508.uJvmXK7U-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=jane.chu@oracle.com \
    --cc=jgg@ziepe.ca \
    --cc=jhubbard@nvidia.com \
    --cc=joao.m.martins@oracle.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=naoya.horiguchi@nec.com \
    --cc=songmuchun@bytedance.com \
    --cc=vishal.l.verma@intel.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