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: Dont poison entire HugeTLB page for single page errors
Date: Thu, 20 Apr 2017 21:48:02 +0800 [thread overview]
Message-ID: <201704202150.DfEKJvdt%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170420110627.12307-1-khandual@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1427 bytes --]
Hi Anshuman,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.11-rc7 next-20170420]
[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-Dont-poison-entire-HugeTLB-page-for-single-page-errors/20170420-204009
config: x86_64-randconfig-x012-201716 (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 'soft_offline_huge_page':
>> mm/memory-failure.c:1605:4: error: implicit declaration of function 'dissolve_free_huge_page' [-Werror=implicit-function-declaration]
dissolve_free_huge_page(hpage);
^~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/dissolve_free_huge_page +1605 mm/memory-failure.c
1599 /* overcommit hugetlb page will be freed to buddy */
1600 SetPageHWPoison(page);
1601 num_poisoned_pages_inc();
1602
1603 if (PageHuge(page)) {
1604 dequeue_hwpoisoned_huge_page(hpage);
> 1605 dissolve_free_huge_page(hpage);
1606 }
1607 }
1608 return ret;
---
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: 32493 bytes --]
next prev parent reply other threads:[~2017-04-20 13:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 3:27 [RFC] mm/madvise: Enable (soft|hard) offline of HugeTLB pages at PGD level Anshuman Khandual
2017-04-19 6:20 ` Aneesh Kumar K.V
2017-04-19 6:42 ` Anshuman Khandual
2017-04-20 5:05 ` Anshuman Khandual
2017-04-20 11:06 ` [PATCH] mm/madvise: Dont poison entire HugeTLB page for single page errors Anshuman Khandual
2017-04-20 13:48 ` kbuild test robot [this message]
2017-05-12 8:10 ` Naoya Horiguchi
2017-05-14 2:34 ` Anshuman Khandual
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=201704202150.DfEKJvdt%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;
as well as URLs for NNTP newsgroup(s).