From: kernel test robot <lkp@intel.com>
To: Lance Yang <ioworker0@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [linux-next:master 9312/9709] rmap.c:undefined reference to `unmap_huge_pmd_locked'
Date: Wed, 1 May 2024 17:22:22 +0800 [thread overview]
Message-ID: <202405011730.KVI5uzFY-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: d04466706db5e241ee026f17b5f920e50dee26b5
commit: 6ae76ae5b2e07d4eb6b3e4fc594856d6500ade54 [9312/9709] mm/vmscan: avoid split lazyfree THP during shrink_folio_list()
config: sparc64-defconfig (https://download.01.org/0day-ci/archive/20240501/202405011730.KVI5uzFY-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240501/202405011730.KVI5uzFY-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202405011730.KVI5uzFY-lkp@intel.com/
Note: the linux-next/master HEAD d04466706db5e241ee026f17b5f920e50dee26b5 builds fine.
It may have been fixed somewhere.
All errors (new ones prefixed by >>):
sparc64-linux-ld: mm/rmap.o: in function `try_to_unmap_one':
>> rmap.c:(.text+0x220c): undefined reference to `unmap_huge_pmd_locked'
>> sparc64-linux-ld: rmap.c:(.text+0x222c): undefined reference to `split_huge_pmd_locked'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-05-01 9:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202405011730.KVI5uzFY-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=ioworker0@gmail.com \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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