linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Shivank Garg <shivankg@amd.com>
Cc: kernel test robot <lkp@intel.com>,
	oe-kbuild-all@lists.linux.dev,
	Linux Memory Management List <linux-mm@kvack.org>,
	Baolin Wang <baolin.wang@linux.alibaba.com>
Subject: Re: [akpm-mm:mm-unstable 36/67] mm/khugepaged.c:2337:7: error: implicit declaration of function 'folio_expected_ref_count'; did you mean 'folio_ref_count'?
Date: Wed, 28 May 2025 11:44:41 -0700	[thread overview]
Message-ID: <20250528114441.abd8980f1d66fcb3e1eaecc2@linux-foundation.org> (raw)
In-Reply-To: <d2ddc44a-19ae-4e4c-90a4-f4ec05558d74@amd.com>

On Wed, 28 May 2025 18:04:02 +0530 Shivank Garg <shivankg@amd.com> wrote:

> On 5/28/2025 5:46 PM, kernel test robot wrote:
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-unstable
> > head:   52ce652e7ab0f015b51fee11b2862507b2c0c25d
> > commit: 3bdddbba5f02f6d97283acb18e2a6e079324fe4b [36/67] mm/khugepaged: fix race with folio split/free using temporary reference
> > config: arm64-randconfig-002-20250528 (https://download.01.org/0day-ci/archive/20250528/202505282015.F0fVmLmH-lkp@intel.com/config)
> > compiler: aarch64-linux-gcc (GCC) 7.5.0
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250528/202505282015.F0fVmLmH-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/202505282015.F0fVmLmH-lkp@intel.com/
> > 
> > Note: the akpm-mm/mm-unstable HEAD 52ce652e7ab0f015b51fee11b2862507b2c0c25d builds fine.
> >       It only hurts bisectability.
> > 
> > All errors (new ones prefixed by >>):
> > 
> >    mm/khugepaged.c: In function 'hpage_collapse_scan_file':
> >>> mm/khugepaged.c:2337:7: error: implicit declaration of function 'folio_expected_ref_count'; did you mean 'folio_ref_count'? [-Werror=implicit-function-declaration]
> >       if (folio_expected_ref_count(folio) + 1 != folio_ref_count(folio)) {
> >           ^~~~~~~~~~~~~~~~~~~~~~~~
> >           folio_ref_count
> >    cc1: some warnings being treated as errors
> > 
> > 
> > vim +2337 mm/khugepaged.c
> 
> folio_expected_ref_count() is introduced with this commit[1] and merged into mm-* tree.
> 
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git/commit/?h=mm-unstable&id=86ebd50224c0734d965843260d0dc057a9431c61
> 

Well darn.  We have a patch in mm-hotfixes-unstable which is cc:stable
(mm-khugepaged-fix-race-with-folio-split-free-using-temporary-reference.patch)
which is dependent upon a patch
(mm-add-folio_expected_ref_count-for-reference-count-calculation.patch)
which is scheduled for 6.16-rc1.

I'll move
mm-khugepaged-fix-race-with-folio-split-free-using-temporary-reference.patch
into mm-stable, after
mm-add-folio_expected_ref_count-for-reference-count-calculation.patch
to remove the bisection hole.  This means that when the -stable
maintainers try to backport
mm-khugepaged-fix-race-with-folio-split-free-using-temporary-reference.patch
into earlier kernels, the build will fail.  When this happens, please
work with them to come up with a version of
mm-khugepaged-fix-race-with-folio-split-free-using-temporary-reference.patch
which is suitable for 6.15 and earlier.



  reply	other threads:[~2025-05-28 18:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-28 12:16 kernel test robot
2025-05-28 12:34 ` Shivank Garg
2025-05-28 18:44   ` Andrew Morton [this message]
2025-05-29  3:46     ` Shivank Garg

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=20250528114441.abd8980f1d66fcb3e1eaecc2@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=shivankg@amd.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