linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Qian Cai (QUIC)" <quic_qiancai@quicinc.com>
To: David Hildenbrand <david@redhat.com>, Oscar Salvador <osalvador@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Anshuman Khandual <anshuman.khandual@arm.com>,
	Vlastimil Babka <vbabka@suse.cz>,
	Michal Hocko <mhocko@kernel.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: RE: Arm64 crash while online/offline memory sections
Date: Tue, 25 May 2021 19:56:35 +0000	[thread overview]
Message-ID: <DM5PR0201MB35570CBA70B13484205FF9C28E259@DM5PR0201MB3557.namprd02.prod.outlook.com> (raw)
In-Reply-To: <8e0dc9de-6834-72aa-364c-50ce1c717437@redhat.com>



> -----Original Message-----
> From: David Hildenbrand <david@redhat.com>
> Sent: Tuesday, May 25, 2021 2:12 PM
> I assume the following will work:
> 
> diff --git a/drivers/base/memory.c b/drivers/base/memory.c
> index b31b3af5c490..6e661d106e96 100644
> --- a/drivers/base/memory.c
> +++ b/drivers/base/memory.c
> @@ -218,14 +218,15 @@ static int memory_block_offline(struct memory_block *mem)
>          struct zone *zone;
>          int ret;
> 
> -       zone = page_zone(pfn_to_page(start_pfn));
> -
>          /*
>           * Unaccount before offlining, such that unpopulated zone and kthreads
>           * can properly be torn down in offline_pages().
>           */
> -       if (nr_vmemmap_pages)
> +       if (nr_vmemmap_pages) {
> +               /* Hotplugged memory has no holes. */
> +               zone = page_zone(pfn_to_page(start_pfn));
>                  adjust_present_page_count(zone, -nr_vmemmap_pages);
> +       }
> 
>          ret = offline_pages(start_pfn + nr_vmemmap_pages,
>                              nr_pages - nr_vmemmap_pages);
> 
> 
> We must not touch pfn_to_page(start_pfn) if it might be a memory hole.
> offline_pages() will make sure there are no holes, but that's too late.

Good catch, David. This patch works well.


  reply	other threads:[~2021-05-25 19:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-25 15:36 Qian Cai (QUIC)
2021-05-25 15:40 ` David Hildenbrand
2021-05-25 16:40   ` Qian Cai (QUIC)
2021-05-25 17:57   ` Qian Cai (QUIC)
2021-05-25 18:00     ` Oscar Salvador
2021-05-25 18:12       ` David Hildenbrand
2021-05-25 19:56         ` Qian Cai (QUIC) [this message]
2021-05-26  7:20         ` Oscar Salvador

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=DM5PR0201MB35570CBA70B13484205FF9C28E259@DM5PR0201MB3557.namprd02.prod.outlook.com \
    --to=quic_qiancai@quicinc.com \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=david@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=osalvador@suse.de \
    --cc=vbabka@suse.cz \
    /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