From: kernel test robot <lkp@intel.com>
To: Naoya Horiguchi <naoya.horiguchi@nec.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [akpm-mm:mm-unstable 244/249] mm/memory-failure.c:1679:59: error: 'SUBPAGE_INDEX_HWPOISON' undeclared
Date: Mon, 4 Jul 2022 14:16:15 +0800 [thread overview]
Message-ID: <202207041434.cdFm3q6k-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-unstable
head: ce4dc6b0378ef1bd305c37c94fb8aabee4c5be04
commit: 43906a2b9553df7799daed304529a6920e97f9e8 [244/249] mm, hwpoison, hugetlb: support saving mechanism of raw error pages
config: parisc-randconfig-r014-20220703 (https://download.01.org/0day-ci/archive/20220704/202207041434.cdFm3q6k-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 11.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git/commit/?id=43906a2b9553df7799daed304529a6920e97f9e8
git remote add akpm-mm https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git
git fetch --no-tags akpm-mm mm-unstable
git checkout 43906a2b9553df7799daed304529a6920e97f9e8
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=parisc SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from include/linux/mmzone.h:21,
from include/linux/gfp.h:6,
from include/linux/mm.h:7,
from mm/memory-failure.c:37:
mm/memory-failure.c: In function 'raw_hwp_list_head':
>> mm/memory-failure.c:1679:59: error: 'SUBPAGE_INDEX_HWPOISON' undeclared (first use in this function)
1679 | return (struct llist_head *)&page_private(hpage + SUBPAGE_INDEX_HWPOISON);
| ^~~~~~~~~~~~~~~~~~~~~~
include/linux/mm_types.h:334:43: note: in definition of macro 'page_private'
334 | #define page_private(page) ((page)->private)
| ^~~~
mm/memory-failure.c:1679:59: note: each undeclared identifier is reported only once for each function it appears in
1679 | return (struct llist_head *)&page_private(hpage + SUBPAGE_INDEX_HWPOISON);
| ^~~~~~~~~~~~~~~~~~~~~~
include/linux/mm_types.h:334:43: note: in definition of macro 'page_private'
334 | #define page_private(page) ((page)->private)
| ^~~~
mm/memory-failure.c:1680:1: error: control reaches end of non-void function [-Werror=return-type]
1680 | }
| ^
cc1: some warnings being treated as errors
vim +/SUBPAGE_INDEX_HWPOISON +1679 mm/memory-failure.c
1676
1677 static inline struct llist_head *raw_hwp_list_head(struct page *hpage)
1678 {
> 1679 return (struct llist_head *)&page_private(hpage + SUBPAGE_INDEX_HWPOISON);
1680 }
1681
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next reply other threads:[~2022-07-04 6:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 6:16 kernel test robot [this message]
2022-07-04 7:03 ` HORIGUCHI NAOYA(堀口 直也)
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=202207041434.cdFm3q6k-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=naoya.horiguchi@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