public inbox for [email protected]
 help / color / mirror / Atom feed
From: kernel test robot <[email protected]>
To: Naoya Horiguchi <[email protected]>
Cc: [email protected], [email protected],
	Ammar Faizi <[email protected]>,
	GNU/Weeb Mailing List <[email protected]>,
	[email protected],
	Andrew Morton <[email protected]>,
	Linux Memory Management List <[email protected]>
Subject: [ammarfaizi2-block:akpm/mm/mm-unstable 480/484] drivers/base/memory.c:186:29: error: no member named 'nr_hwpoison' in 'struct memory_block'
Date: Fri, 23 Sep 2022 12:52:14 +0800	[thread overview]
Message-ID: <[email protected]> (raw)

tree:   https://github.com/ammarfaizi2/linux-block akpm/mm/mm-unstable
head:   1dee68cfead9a3a85e244a274b4e85620abd5331
commit: 69b496f03bb46c7ce743aff0d976c078d753d6d6 [480/484] mm/hwpoison: introduce per-memory_block hwpoison counter
config: x86_64-randconfig-a016 (https://download.01.org/0day-ci/archive/20220923/[email protected]/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/ammarfaizi2/linux-block/commit/69b496f03bb46c7ce743aff0d976c078d753d6d6
        git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
        git fetch --no-tags ammarfaizi2-block akpm/mm/mm-unstable
        git checkout 69b496f03bb46c7ce743aff0d976c078d753d6d6
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash

If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <[email protected]>

All errors (new ones prefixed by >>):

>> drivers/base/memory.c:186:29: error: no member named 'nr_hwpoison' in 'struct memory_block'
           if (atomic_long_read(&mem->nr_hwpoison))
                                 ~~~  ^
   drivers/base/memory.c:870:49: error: no member named 'nr_hwpoison' in 'struct memory_block'
                   clear_hwpoisoned_pages(atomic_long_read(&mem->nr_hwpoison));
                                                            ~~~  ^
   2 errors generated.


vim +186 drivers/base/memory.c

   177	
   178	static int memory_block_online(struct memory_block *mem)
   179	{
   180		unsigned long start_pfn = section_nr_to_pfn(mem->start_section_nr);
   181		unsigned long nr_pages = PAGES_PER_SECTION * sections_per_block;
   182		unsigned long nr_vmemmap_pages = mem->nr_vmemmap_pages;
   183		struct zone *zone;
   184		int ret;
   185	
 > 186		if (atomic_long_read(&mem->nr_hwpoison))
   187			return -EHWPOISON;
   188	
   189		zone = zone_for_pfn_range(mem->online_type, mem->nid, mem->group,
   190					  start_pfn, nr_pages);
   191	
   192		/*
   193		 * Although vmemmap pages have a different lifecycle than the pages
   194		 * they describe (they remain until the memory is unplugged), doing
   195		 * their initialization and accounting at memory onlining/offlining
   196		 * stage helps to keep accounting easier to follow - e.g vmemmaps
   197		 * belong to the same zone as the memory they backed.
   198		 */
   199		if (nr_vmemmap_pages) {
   200			ret = mhp_init_memmap_on_memory(start_pfn, nr_vmemmap_pages, zone);
   201			if (ret)
   202				return ret;
   203		}
   204	
   205		ret = online_pages(start_pfn + nr_vmemmap_pages,
   206				   nr_pages - nr_vmemmap_pages, zone, mem->group);
   207		if (ret) {
   208			if (nr_vmemmap_pages)
   209				mhp_deinit_memmap_on_memory(start_pfn, nr_vmemmap_pages);
   210			return ret;
   211		}
   212	
   213		/*
   214		 * Account once onlining succeeded. If the zone was unpopulated, it is
   215		 * now already properly populated.
   216		 */
   217		if (nr_vmemmap_pages)
   218			adjust_present_page_count(pfn_to_page(start_pfn), mem->group,
   219						  nr_vmemmap_pages);
   220	
   221		mem->zone = zone;
   222		return ret;
   223	}
   224	

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

                 reply	other threads:[~2022-09-23  4:52 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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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