From: Andrew Morton <akpm@linux-foundation.org>
To: kbuild test robot <lkp@intel.com>
Cc: Michael Holzheu <holzheu@linux.vnet.ibm.com>,
kbuild-all@01.org, Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Gerald Schaefer <gerald.schaefer@de.ibm.com>,
linux-mm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] numa: fix /proc/<pid>/numa_maps on s390
Date: Wed, 20 Jan 2016 12:26:31 -0800 [thread overview]
Message-ID: <20160120122631.e9c8a842d36d6dba4bb25964@linux-foundation.org> (raw)
In-Reply-To: <201601210354.l5qn10aD%fengguang.wu@intel.com>
On Thu, 21 Jan 2016 03:32:41 +0800 kbuild test robot <lkp@intel.com> wrote:
> Hi Michael,
>
> [auto build test ERROR on next-20160120]
> [cannot apply to v4.4-rc8 v4.4-rc7 v4.4-rc6 v4.4]
> [if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
>
> url: https://github.com/0day-ci/linux/commits/Michael-Holzheu/numa-fix-proc-pid-numa_maps-on-s390/20160121-022313
> config: ia64-alldefconfig (attached as .config)
> reproduce:
> wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # save the attached .config to linux build tree
> make.cross ARCH=ia64
>
> All errors (new ones prefixed by >>):
>
> fs/proc/task_mmu.c: In function 'gather_pte_stats':
> >> fs/proc/task_mmu.c:1523:3: error: implicit declaration of function 'huge_ptep_get' [-Werror=implicit-function-declaration]
> pte_t huge_pte = huge_ptep_get((pte_t *)pmd);
> ^
hm.
That whole code block in gather_pte_stats() just shouldn't exist when
CONFIG_TRANSPARENT_HUGEPAGE=n. And because pmd_trans_huge_lock()
returns NULL, the compiler will nuke it all anyway.
So instead of doing the obvious:
--- a/fs/proc/task_mmu.c~numa-fix-proc-pid-numa_maps-on-s390-fix
+++ a/fs/proc/task_mmu.c
@@ -1524,7 +1524,11 @@ static int gather_pte_stats(pmd_t *pmd,
ptl = pmd_trans_huge_lock(pmd, vma);
if (ptl) {
+#ifdef CONFIG_HUGETLB_PAGE
pte_t huge_pte = huge_ptep_get((pte_t *)pmd);
+#else
+ pte_t huge_pte = *(pte_t *)pmd;
+#endif
struct page *page;
page = can_gather_numa_stats(huge_pte, vma, addr);
I'm thinking we should do
--- a/fs/proc/task_mmu.c~numa-fix-proc-pid-numa_maps-on-s390-fix
+++ a/fs/proc/task_mmu.c
@@ -1523,6 +1523,7 @@ static int gather_pte_stats(pmd_t *pmd,
pte_t *pte;
ptl = pmd_trans_huge_lock(pmd, vma);
+#ifdef CONFIG_TRANSPARENT_HUGEPAGE
if (ptl) {
pte_t huge_pte = huge_ptep_get((pte_t *)pmd);
struct page *page;
@@ -1534,6 +1535,7 @@ static int gather_pte_stats(pmd_t *pmd,
spin_unlock(ptl);
return 0;
}
+#endif
if (pmd_trans_unstable(pmd))
return 0;
_
next prev parent reply other threads:[~2016-01-20 20:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 18:17 [PATCH] numa: fix /proc/<pid>/numa_maps on s390 Michael Holzheu
2016-01-20 19:32 ` kbuild test robot
2016-01-20 20:26 ` Andrew Morton [this message]
2016-01-21 14:57 ` Gerald Schaefer
2016-01-21 19:19 ` Andrew Morton
2016-01-22 13:37 ` Gerald Schaefer
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=20160120122631.e9c8a842d36d6dba4bb25964@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=gerald.schaefer@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=holzheu@linux.vnet.ibm.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@vger.kernel.org \
--cc=lkp@intel.com \
--cc=schwidefsky@de.ibm.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).