Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: kernel test robot <lkp@intel.com>
Cc: Anshuman Khandual <anshuman.khandual@arm.com>,
	oe-kbuild-all@lists.linux.dev,
	David Hildenbrand <david@kernel.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	mm-commits@vger.kernel.org,
	Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: [akpm-mm:mm-new 661/679] mmu.c:undefined reference to `__check_safe_pte_update'
Date: Sun, 27 Sep 2026 13:31:00 -0700	[thread overview]
Message-ID: <20260927133100.46a4f7067c79280dcf83731b@linux-foundation.org> (raw)
In-Reply-To: <202609270030.Y0QVBPmK-lkp@intel.com>

On Sun, 27 Sep 2026 00:32:54 +0800 kernel test robot <lkp@intel.com> wrote:

> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-new
> head:   b4fc90c82982d98959af08b4320420bcfc01303b
> commit: 2862bcaf1aca55e0b43a5692a4595281ab780f05 [661/679] arm64/mm: move __check_safe_pte_update()
> config: arm64-randconfig-1002-20260926 (https://download.01.org/0day-ci/archive/20260927/202609270030.Y0QVBPmK-lkp@intel.com/config)
> compiler: aarch64-linux-gcc (GCC) 8.5.0

Thanks.  It works for me, but I'm using gcc-15.2.0.

> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260927/202609270030.Y0QVBPmK-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/202609270030.Y0QVBPmK-lkp@intel.com/
> 
> All errors (new ones prefixed by >>):
> 
> >> aarch64-linux-ld: Unexpected GOT/PLT entries detected!
> >> aarch64-linux-ld: Unexpected run-time procedure linkages detected!
>    aarch64-linux-ld: arch/arm64/mm/mmu.o: in function `__set_ptes_anysz.isra.40.constprop.47':
> >> mmu.c:(.text+0x9a8): undefined reference to `__check_safe_pte_update'
>    aarch64-linux-ld: arch/arm64/mm/hugetlbpage.o: in function `__set_ptes_anysz.isra.32':
> >> hugetlbpage.c:(.text+0x1a8): undefined reference to `__check_safe_pte_update'
>    aarch64-linux-ld: kernel/bpf/arena.o: in function `apply_range_set_cb':
> >> arena.c:(.text+0x11fc): undefined reference to `__check_safe_pte_update'
>    aarch64-linux-ld: mm/gup.o: in function `follow_page_pte':
> >> gup.c:(.text+0x2b48): undefined reference to `__check_safe_pte_update'
>    aarch64-linux-ld: mm/memory.o: in function `__set_ptes.isra.207':
> >> memory.c:(.text+0x3418): undefined reference to `__check_safe_pte_update'
>    aarch64-linux-ld: mm/mprotect.o:mprotect.c:(.text+0x1080): more undefined references to `__check_safe_pte_update' follow
> 



  reply	other threads:[~2026-09-27 20:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-26 16:32 [akpm-mm:mm-new 661/679] mmu.c:undefined reference to `__check_safe_pte_update' kernel test robot
2026-09-27 20:31 ` Andrew Morton [this message]
2026-09-28  4:42   ` Anshuman Khandual
2026-09-28  7:44     ` David Hildenbrand (Arm)

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=20260927133100.46a4f7067c79280dcf83731b@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=david@kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --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