linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Anshuman Khandual <khandual@linux.vnet.ibm.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, n-horiguchi@ah.jp.nec.com,
	akpm@linux-foundation.org, aneesh.kumar@linux.vnet.ibm.com
Subject: Re: [PATCH] mm/madvise: Enable (soft|hard) offline of HugeTLB pages at PGD level
Date: Wed, 26 Apr 2017 09:31:45 +0800	[thread overview]
Message-ID: <201704260926.ILuEWnr6%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170425111315.12480-1-khandual@linux.vnet.ibm.com>

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

Hi Anshuman,

[auto build test ERROR on linus/master]
[also build test ERROR on v4.11-rc8 next-20170424]
[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/Anshuman-Khandual/mm-madvise-Enable-soft-hard-offline-of-HugeTLB-pages-at-PGD-level/20170425-224016
config: x86_64-kexec (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

   mm/memory-failure.c: In function 'new_page':
>> mm/memory-failure.c:1485:7: error: implicit declaration of function 'hstate_is_gigantic' [-Werror=implicit-function-declaration]
      if (hstate_is_gigantic(page_hstate(compound_head(p))))
          ^~~~~~~~~~~~~~~~~~
   cc1: some warnings being treated as errors

vim +/hstate_is_gigantic +1485 mm/memory-failure.c

  1479	EXPORT_SYMBOL(unpoison_memory);
  1480	
  1481	static struct page *new_page(struct page *p, unsigned long private, int **x)
  1482	{
  1483		int nid = page_to_nid(p);
  1484		if (PageHuge(p)) {
> 1485			if (hstate_is_gigantic(page_hstate(compound_head(p))))
  1486				return alloc_huge_page_nonid(page_hstate(compound_head(p)));
  1487	
  1488			return alloc_huge_page_node(page_hstate(compound_head(p)),

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

      reply	other threads:[~2017-04-26  1:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-25 11:13 Anshuman Khandual
2017-04-26  1: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=201704260926.ILuEWnr6%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=kbuild-all@01.org \
    --cc=khandual@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=n-horiguchi@ah.jp.nec.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