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 892f5b3b07e5b07f2f29c87750ff94fa58dcab73
Date: Thu, 17 Sep 2026 09:22:37 -0700 [thread overview]
Message-ID: <20260917092237.5ba48bf16e8406e3753eacaf@linux-foundation.org> (raw)
In-Reply-To: <202609171758.049ApqPm-lkp@intel.com>
On Thu, 17 Sep 2026 18:00:02 +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: 892f5b3b07e5b07f2f29c87750ff94fa58dcab73 mm/swap, PM: hibernate: atomically replace hibernation pin
>
> Error/Warning (recently discovered and may have been fixed):
>
> https://lore.kernel.org/oe-kbuild-all/202609171159.oaB1OaSG-lkp@intel.com
>
> fs/proc/task_mmu.c:3448: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: call to undeclared function 'reacquire_rcu'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
argh, we already fixed this five times.
Confirmed with x86_64 and
https://download.01.org/0day-ci/archive/20260917/202609171159.oaB1OaSG-lkp@intel.com/config
Suren, I'll drop the series. Please check this (and the 'lock_ctx_mm'
defined but not used failure) when preparing the planned respin.
next prev parent reply other threads:[~2026-09-17 16:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 10:00 [akpm-mm:mm-new] BUILD REGRESSION 892f5b3b07e5b07f2f29c87750ff94fa58dcab73 kernel test robot
2026-09-17 16:22 ` Andrew Morton [this message]
2026-09-17 16:57 ` Suren Baghdasaryan
2026-09-18 15:36 ` 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=20260917092237.5ba48bf16e8406e3753eacaf@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