mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, "Luck, Tony" <tony.luck@intel.com>
Subject: Re: [PATCH] mm: Check if section present during memory block (un)registering
Date: Tue, 25 Aug 2015 16:08:33 -0700	[thread overview]
Message-ID: <20150825160833.ac6a07ddc524e7fdbb6847de@linux-foundation.org> (raw)
In-Reply-To: <1440542476-15169-1-git-send-email-yinghai@kernel.org>

On Tue, 25 Aug 2015 15:41:16 -0700 Yinghai Lu <yinghai@kernel.org> wrote:

> Tony found on his setup, if memory block size 512M will cause crash
> during booting.
> 
>  BUG: unable to handle kernel paging request at ffffea0074000020
>  IP: [<ffffffff81670527>] get_nid_for_pfn+0x17/0x40
>  PGD 128ffcb067 PUD 128ffc9067 PMD 0 
>  Oops: 0000 [#1] SMP 
>  Modules linked in:
>  CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.2.0-rc8 #1
> ...
>  Call Trace:
>   [<ffffffff81453b56>] ? register_mem_sect_under_node+0x66/0xe0
>   [<ffffffff81453eeb>] register_one_node+0x17b/0x240
>   [<ffffffff81b1f1ed>] ? pci_iommu_alloc+0x6e/0x6e
>   [<ffffffff81b1f229>] topology_init+0x3c/0x95
>   [<ffffffff8100213d>] do_one_initcall+0xcd/0x1f0
> 
> The system has non continuous RAM address:
>  BIOS-e820: [mem 0x0000001300000000-0x0000001cffffffff] usable
>  BIOS-e820: [mem 0x0000001d70000000-0x0000001ec7ffefff] usable
>  BIOS-e820: [mem 0x0000001f00000000-0x0000002bffffffff] usable
>  BIOS-e820: [mem 0x0000002c18000000-0x0000002d6fffefff] usable
>  BIOS-e820: [mem 0x0000002e00000000-0x00000039ffffffff] usable
> 
> So there are start sections in memory block not present.
> For example:
> memory block : [0x2c18000000, 0x2c20000000) 512M
> first three sections are not present.
> 
> Current register_mem_sect_under_node() assume first section is present,
> but memory block section number range [start_section_nr, end_section_nr]
> would include not present section.
> 
> For arch that support vmemmap, we don't setup memmap for struct page area
> within not present sections area.
> 
> So skip the pfn range that belong to not present section.
> 
> Als fixes unregister_mem_sect_under_nodes().

It appears this should be backported into -stable kernels, yes?  Do you
know which kernel versions need the fix?

> --- a/drivers/base/node.c
> +++ b/drivers/base/node.c
> @@ -390,8 +390,14 @@ int register_mem_sect_under_node(struct memory_block *mem_blk, int nid)
>  	sect_end_pfn = section_nr_to_pfn(mem_blk->end_section_nr);
>  	sect_end_pfn += PAGES_PER_SECTION - 1;
>  	for (pfn = sect_start_pfn; pfn <= sect_end_pfn; pfn++) {
> -		int page_nid;
> +		int page_nid, scn_nr;
>  
> +		scn_nr = pfn_to_section_nr(pfn);
> +		if (!present_section_nr(scn_nr)) {
> +			pfn = round_down(pfn + PAGES_PER_SECTION,
> +					 PAGES_PER_SECTION) - 1;
> +			continue;
> +		}

Can we please add a comment here telling readers why this is being
done?  What scenario is being detected and how it comes about.

>  		page_nid = get_nid_for_pfn(pfn);
>  		if (page_nid < 0)
>  			continue;


  reply	other threads:[~2015-08-25 23:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-25 22:41 Yinghai Lu
2015-08-25 23:08 ` Andrew Morton [this message]
2015-08-25 23:24   ` Luck, Tony
2015-08-26  4:04   ` Yinghai Lu

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=20150825160833.ac6a07ddc524e7fdbb6847de@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@intel.com \
    --cc=yinghai@kernel.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

all inboxes | Powered by JetHome®