linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>
Cc: oe-kbuild-all@lists.linux.dev,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 3561/4143] mm/sparse.c:730:24: error: implicit declaration of function 'bootmem_type'
Date: Sat, 12 Oct 2024 05:47:09 +0800	[thread overview]
Message-ID: <202410120526.Ud7TRejf-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   d61a00525464bfc5fe92c6ad713350988e492b88
commit: 8010bda4cd9c0dded1cb1e52ac1d14f4e6a55ec9 [3561/4143] bootmem: stop using page->index
config: loongarch-randconfig-r061-20241012 (https://download.01.org/0day-ci/archive/20241012/202410120526.Ud7TRejf-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241012/202410120526.Ud7TRejf-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/202410120526.Ud7TRejf-lkp@intel.com/

All errors (new ones prefixed by >>):

   mm/sparse.c: In function 'free_map_bootmem':
>> mm/sparse.c:730:24: error: implicit declaration of function 'bootmem_type' [-Wimplicit-function-declaration]
     730 |                 type = bootmem_type(page);
         |                        ^~~~~~~~~~~~
>> mm/sparse.c:735:39: error: implicit declaration of function 'bootmem_info' [-Wimplicit-function-declaration]
     735 |                 removing_section_nr = bootmem_info(page);
         |                                       ^~~~~~~~~~~~


vim +/bootmem_type +730 mm/sparse.c

   719	
   720	static void free_map_bootmem(struct page *memmap)
   721	{
   722		unsigned long maps_section_nr, removing_section_nr, i;
   723		unsigned long type, nr_pages;
   724		struct page *page = virt_to_page(memmap);
   725	
   726		nr_pages = PAGE_ALIGN(PAGES_PER_SECTION * sizeof(struct page))
   727			>> PAGE_SHIFT;
   728	
   729		for (i = 0; i < nr_pages; i++, page++) {
 > 730			type = bootmem_type(page);
   731	
   732			BUG_ON(type == NODE_INFO);
   733	
   734			maps_section_nr = pfn_to_section_nr(page_to_pfn(page));
 > 735			removing_section_nr = bootmem_info(page);
   736	
   737			/*
   738			 * When this function is called, the removing section is
   739			 * logical offlined state. This means all pages are isolated
   740			 * from page allocator. If removing section's memmap is placed
   741			 * on the same section, it must not be freed.
   742			 * If it is freed, page allocator may allocate it which will
   743			 * be removed physically soon.
   744			 */
   745			if (maps_section_nr != removing_section_nr)
   746				put_page_bootmem(page);
   747		}
   748	}
   749	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


                 reply	other threads:[~2024-10-11 21:47 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=202410120526.Ud7TRejf-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=willy@infradead.org \
    /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