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: David Hildenbrand <david@kernel.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	mm-commits@vger.kernel.org,
	Suren Baghdasaryan <surenb@google.com>
Subject: Re: [akpm-mm:mm-new] BUILD REGRESSION b4fc90c82982d98959af08b4320420bcfc01303b
Date: Sun, 27 Sep 2026 11:04:07 -0700	[thread overview]
Message-ID: <20260927110407.8641fb46613365094f4d32ff@linux-foundation.org> (raw)
In-Reply-To: <202609271644.eX9EFdJw-lkp@intel.com>

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

> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-new
> branch HEAD: b4fc90c82982d98959af08b4320420bcfc01303b  mm/swap, PM: hibernate: atomically replace hibernation pin
> 
> Error/Warning (recently discovered and may have been fixed):
> 
>     https://lore.kernel.org/oe-kbuild-all/202609160337.WJiD9BqX-lkp@intel.com
>     https://lore.kernel.org/oe-kbuild-all/202609171159.oaB1OaSG-lkp@intel.com
>     https://lore.kernel.org/oe-kbuild-all/202609270030.Y0QVBPmK-lkp@intel.com
> 
>     aarch64-linux-ld: Unexpected GOT/PLT entries detected!
>     aarch64-linux-ld: Unexpected run-time procedure linkages detected!
>     arena.c:(.text+0x11fc): undefined reference to `__check_safe_pte_update'
>     fs/proc/task_mmu.c:3450:17: error: implicit declaration of function 'drop_rcu' [-Werror=implicit-function-declaration]
>     fs/proc/task_mmu.c:3450:3: error: call to undeclared function 'drop_rcu'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
>     fs/proc/task_mmu.c:3450:3: error: implicit declaration of function 'drop_rcu'; did you mean 'drop_slab'? [-Werror=implicit-function-declaration]
>     fs/proc/task_mmu.c:3452:17: error: implicit declaration of function 'reacquire_rcu' [-Werror=implicit-function-declaration]
>     fs/proc/task_mmu.c:3452:3: error: call to undeclared function 'reacquire_rcu'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
>     fs/proc/task_mmu.c:3452:3: error: implicit declaration of function 'reacquire_rcu'; did you mean 'get_file_rcu'? [-Werror=implicit-function-declaration]
>     gup.c:(.text+0x2b48): undefined reference to `__check_safe_pte_update'
>     hugetlbpage.c:(.text+0x1a8): undefined reference to `__check_safe_pte_update'
>     memory.c:(.text+0x3418): undefined reference to `__check_safe_pte_update'
>     mmu.c:(.text+0x9a8): undefined reference to `__check_safe_pte_update'

Thanks.  Against "proc/task_mmu: remove unnecessary inlines in function
definitions":


From: Andrew Morton <akpm@linux-foundation.org>
Subject: proc-task_mmu-remove-unnecessary-inlines-in-function-definitions-fix
Date: Sun Sep 27 10:59:53 AM PDT 2026

fix CONFIG_NUMA=y && CONFIG_PROC_PAGE_MONITOR=n build

show_numa_map() uses drop_rcu() and reacquire_rcu(), but those helpers are
currently built only when CONFIG_PROC_PAGE_MONITOR is enabled.  A kernel
with CONFIG_NUMA=y and CONFIG_PROC_PAGE_MONITOR=n therefore fails to build
with implicit declarations for both helpers.

Cc: Suren Baghdasaryan <surenb@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 fs/proc/task_mmu.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/fs/proc/task_mmu.c~proc-task_mmu-remove-unnecessary-inlines-in-function-definitions-fix
+++ a/fs/proc/task_mmu.c
@@ -196,7 +196,7 @@ static bool fallback_to_mmap_lock(struct
 	return true;
 }
 
-#ifdef CONFIG_PROC_PAGE_MONITOR
+#if defined(CONFIG_PROC_PAGE_MONITOR) || defined(CONFIG_NUMA)
 static void drop_rcu(struct proc_maps_private *priv)
 {
 	if (priv->lock_ctx.mmap_locked)
_



  reply	other threads:[~2026-09-27 18:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-27  8:00 [akpm-mm:mm-new] BUILD REGRESSION b4fc90c82982d98959af08b4320420bcfc01303b kernel test robot
2026-09-27 18:04 ` Andrew Morton [this message]
2026-09-27 18:42   ` Suren Baghdasaryan

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=20260927110407.8641fb46613365094f4d32ff@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=david@kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=mm-commits@vger.kernel.org \
    --cc=surenb@google.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