From: kbuild test robot <lkp@intel.com>
To: Minchan Kim <minchan@kernel.org>
Cc: kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [mmotm:master 80/120] mm/madvise.c:45:7: error: 'MADV_PAGEOUT' undeclared; did you mean 'MADV_RANDOM'?
Date: Thu, 25 Jul 2019 17:38:27 +0800 [thread overview]
Message-ID: <201907251759.zSy10dLW%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3690 bytes --]
tree: git://git.cmpxchg.org/linux-mmotm.git master
head: 79b3e476080beb7faf41bddd6c3d7059cd1a5f31
commit: 174e3844d80cb220a226da1e5adb956c80a6d7ca [80/120] mm, madvise: introduce MADV_PAGEOUT
config: parisc-c3000_defconfig (attached as .config)
compiler: hppa-linux-gcc (GCC) 7.4.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 174e3844d80cb220a226da1e5adb956c80a6d7ca
# save the attached .config to linux build tree
GCC_VERSION=7.4.0 make.cross ARCH=parisc
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
mm/madvise.c: In function 'madvise_need_mmap_write':
mm/madvise.c:44:7: error: 'MADV_COLD' undeclared (first use in this function); did you mean 'MADV_FREE'?
case MADV_COLD:
^~~~~~~~~
MADV_FREE
mm/madvise.c:44:7: note: each undeclared identifier is reported only once for each function it appears in
>> mm/madvise.c:45:7: error: 'MADV_PAGEOUT' undeclared (first use in this function); did you mean 'MADV_RANDOM'?
case MADV_PAGEOUT:
^~~~~~~~~~~~
MADV_RANDOM
mm/madvise.c: In function 'madvise_cold_pte_range':
mm/madvise.c:334:7: error: implicit declaration of function 'is_huge_zero_pmd'; did you mean 'is_huge_zero_pud'? [-Werror=implicit-function-declaration]
if (is_huge_zero_pmd(orig_pmd))
^~~~~~~~~~~~~~~~
is_huge_zero_pud
mm/madvise.c:361:7: error: implicit declaration of function 'pmd_young'; did you mean 'pte_young'? [-Werror=implicit-function-declaration]
if (pmd_young(orig_pmd)) {
^~~~~~~~~
pte_young
mm/madvise.c:363:15: error: implicit declaration of function 'pmd_mkold'; did you mean 'pte_mkold'? [-Werror=implicit-function-declaration]
orig_pmd = pmd_mkold(orig_pmd);
^~~~~~~~~
pte_mkold
mm/madvise.c:363:13: error: incompatible types when assigning to type 'pmd_t {aka struct <anonymous>}' from type 'int'
orig_pmd = pmd_mkold(orig_pmd);
^
mm/madvise.c:365:4: error: implicit declaration of function 'set_pmd_at'; did you mean 'set_pte_at'? [-Werror=implicit-function-declaration]
set_pmd_at(mm, addr, pmd, orig_pmd);
^~~~~~~~~~
set_pte_at
mm/madvise.c: In function 'madvise_pageout_pte_range':
mm/madvise.c:538:13: error: incompatible types when assigning to type 'pmd_t {aka struct <anonymous>}' from type 'int'
orig_pmd = pmd_mkold(orig_pmd);
^
mm/madvise.c: In function 'madvise_vma':
mm/madvise.c:1063:7: error: 'MADV_COLD' undeclared (first use in this function); did you mean 'MADV_FREE'?
case MADV_COLD:
^~~~~~~~~
MADV_FREE
mm/madvise.c:1065:7: error: 'MADV_PAGEOUT' undeclared (first use in this function); did you mean 'MADV_RANDOM'?
case MADV_PAGEOUT:
^~~~~~~~~~~~
MADV_RANDOM
mm/madvise.c: In function 'madvise_behavior_valid':
mm/madvise.c:1088:7: error: 'MADV_COLD' undeclared (first use in this function); did you mean 'MADV_FREE'?
case MADV_COLD:
^~~~~~~~~
MADV_FREE
mm/madvise.c:1089:7: error: 'MADV_PAGEOUT' undeclared (first use in this function); did you mean 'MADV_RANDOM'?
case MADV_PAGEOUT:
^~~~~~~~~~~~
MADV_RANDOM
cc1: some warnings being treated as errors
vim +45 mm/madvise.c
---
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: 15672 bytes --]
next reply other threads:[~2019-07-25 9:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 9:38 kbuild test robot [this message]
2019-07-26 0:12 ` Andrew Morton
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=201907251759.zSy10dLW%lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.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