From: kernel test robot <lkp@intel.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: oe-kbuild-all@lists.linux.dev,
David Hildenbrand <david@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
mm-commits@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>
Subject: [akpm-mm:mm-new 661/676] ld.lld: error: undefined symbol: __check_safe_pte_update
Date: Fri, 25 Sep 2026 17:38:47 +0200 [thread overview]
Message-ID: <202609251702.X00bYqkV-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-new
head: 2589c5593c200e5146db848730baa1d7dd0c9f4e
commit: f0284d9baaf7144fa87bc9ef9f3c64ccfd9600e1 [661/676] arm64/mm: move __check_safe_pte_update()
config: arm64-randconfig-r2200-20260925 (https://download.01.org/0day-ci/archive/20260925/202609251702.X00bYqkV-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 7e4b8ae111298941e0c31052a7124ab36f5365b5)
smatch: v0.5.0-9187-g5189e3fb
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260925/202609251702.X00bYqkV-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/202609251702.X00bYqkV-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: undefined symbol: __check_safe_pte_update
>>> referenced by pgtable.h:659 (arch/arm64/include/asm/pgtable.h:659)
>>> arch/arm64/mm/mmu.o:(modify_prot_commit_ptes) in archive vmlinux.a
>>> referenced by pgtable.h:659 (arch/arm64/include/asm/pgtable.h:659)
>>> arch/arm64/mm/mmu.o:(modify_prot_commit_ptes) in archive vmlinux.a
>>> referenced by pgtable.h:659 (arch/arm64/include/asm/pgtable.h:659)
>>> kernel/bpf/arena.o:(apply_range_set_cb) in archive vmlinux.a
>>> referenced 57 more times
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-25 15:39 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=202609251702.X00bYqkV-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=david@kernel.org \
--cc=linux-mm@kvack.org \
--cc=mm-commits@vger.kernel.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