linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: kbuild-all@01.org, linux-mm@kvack.org,
	linux-arm-kernel@lists.infradead.org, akpm@linux-foundation.org,
	mhocko@suse.com, mingo@kernel.org, labbott@fedoraproject.org,
	catalin.marinas@arm.com, will.deacon@arm.com,
	mark.rutland@arm.com, zhongjiang@huawei.com,
	guohanjun@huawei.com, tanxiaojun@huawei.com,
	steve.capper@linaro.org
Subject: Re: [PATCH v2] mm: vmalloc: make vmalloc_to_page() deal with PMD/PUD mappings
Date: Sat, 3 Jun 2017 06:31:53 +0800	[thread overview]
Message-ID: <201706030608.koMVDa7j%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170602155416.32706-1-ard.biesheuvel@linaro.org>

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

Hi Ard,

[auto build test ERROR on mmotm/master]
[also build test ERROR on v4.12-rc3 next-20170602]
[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/Ard-Biesheuvel/mm-vmalloc-make-vmalloc_to_page-deal-with-PMD-PUD-mappings/20170603-021745
base:   git://git.cmpxchg.org/linux-mmotm.git master
config: parisc-allmodconfig (attached as .config)
compiler: hppa-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
        wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        make.cross ARCH=parisc 

All error/warnings (new ones prefixed by >>):

   In file included from arch/parisc/include/asm/pgtable.h:4:0,
                    from include/linux/mm.h:70,
                    from mm/vmalloc.c:12:
   mm/vmalloc.c: In function 'vmalloc_to_page':
>> include/asm-generic/4level-fixup.h:26:25: error: implicit declaration of function 'pgd_page' [-Werror=implicit-function-declaration]
    #define pud_page(pud)   pgd_page(pud)
                            ^
>> mm/vmalloc.c:295:10: note: in expansion of macro 'pud_page'
      return pud_page(*pud) + ((addr & ~PUD_MASK) >> PAGE_SHIFT);
             ^~~~~~~~
>> mm/vmalloc.c:295:25: warning: return makes pointer from integer without a cast [-Wint-conversion]
      return pud_page(*pud) + ((addr & ~PUD_MASK) >> PAGE_SHIFT);
                             
   cc1: some warnings being treated as errors

vim +/pud_page +295 mm/vmalloc.c

   279		/*
   280		 * XXX we might need to change this if we add VIRTUAL_BUG_ON for
   281		 * architectures that do not vmalloc module space
   282		 */
   283		VIRTUAL_BUG_ON(!is_vmalloc_or_module_addr(vmalloc_addr));
   284	
   285		if (pgd_none(*pgd))
   286			return NULL;
   287		p4d = p4d_offset(pgd, addr);
   288		if (p4d_none(*p4d))
   289			return NULL;
   290		pud = pud_offset(p4d, addr);
   291		if (pud_none(*pud))
   292			return NULL;
   293		if (pud_huge(*pud)) {
   294			VM_BUG_ON(!IS_ENABLED(CONFIG_HAVE_ARCH_HUGE_VMAP));
 > 295			return pud_page(*pud) + ((addr & ~PUD_MASK) >> PAGE_SHIFT);
   296		}
   297		pmd = pmd_offset(pud, addr);
   298		if (pmd_none(*pmd))
   299			return NULL;
   300		if (pmd_huge(*pmd)) {
   301			VM_BUG_ON(!IS_ENABLED(CONFIG_HAVE_ARCH_HUGE_VMAP));
   302			return pmd_page(*pmd) + ((addr & ~PMD_MASK) >> PAGE_SHIFT);
   303		}

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

      parent reply	other threads:[~2017-06-02 22:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-02 15:54 Ard Biesheuvel
2017-06-02 17:30 ` Mark Rutland
2017-06-02 22:00 ` kbuild test robot
2017-06-02 22:31 ` kbuild test robot [this message]

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=201706030608.koMVDa7j%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=ard.biesheuvel@linaro.org \
    --cc=catalin.marinas@arm.com \
    --cc=guohanjun@huawei.com \
    --cc=kbuild-all@01.org \
    --cc=labbott@fedoraproject.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mm@kvack.org \
    --cc=mark.rutland@arm.com \
    --cc=mhocko@suse.com \
    --cc=mingo@kernel.org \
    --cc=steve.capper@linaro.org \
    --cc=tanxiaojun@huawei.com \
    --cc=will.deacon@arm.com \
    --cc=zhongjiang@huawei.com \
    /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