From: Pingfan Liu <kernelfans@gmail.com>
To: David Hildenbrand <david@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, Dan Williams <dan.j.williams@intel.com>,
Oscar Salvador <osalvador@suse.de>,
Michal Hocko <mhocko@kernel.org>, Pingfan Liu <piliu@redhat.com>
Subject: Re: [PATCH v1] mm/memory_hotplug: Don't free usage map when removing a re-added early section
Date: Wed, 8 Jan 2020 17:11:28 +0800 [thread overview]
Message-ID: <CAFgQCTvp0rFo2TQqp1M1k3x5OPi-ND5LMFVv8WirHL6M4mHcUg@mail.gmail.com> (raw)
In-Reply-To: <c9be027b-a2a4-44b7-1eda-83a8fd0bf87a@redhat.com>
On Wed, Jan 8, 2020 at 4:24 PM David Hildenbrand <david@redhat.com> wrote:
>
>
> We have another reproducer that is used more frequently than memtrace :)
>
> Using Dynamic Memory under a Power DLAPR can trigger it easily.
> Triggering removal (I assume after previously removed+re-added) of
> memory from the HMC GUI can crash the kernel with the same call trace
> and is fixed by this patch.
>
> CCing Pingfan who verified that this patch fixes the issue - maybe he
> wants to provide a Tested-by:
Yes, this patch fixes the hot remove+add+remove bug on POWERVM, which
can be reproduced by dlpar.
Tested-by: Pingfan Liu <piliu@redhat.com>
>
> @Andrew, any chance we can get this upstream soon-ish? Thanks!
>
> --
> Thanks,
>
> David / dhildenb
>
prev parent reply other threads:[~2020-01-08 9:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 10:46 David Hildenbrand
2019-12-18 3:21 ` Dan Williams
2019-12-18 8:53 ` David Hildenbrand
2019-12-18 12:06 ` David Hildenbrand
2019-12-18 12:06 ` David Hildenbrand
2020-01-08 8:19 ` David Hildenbrand
2020-01-08 9:11 ` Pingfan Liu [this message]
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=CAFgQCTvp0rFo2TQqp1M1k3x5OPi-ND5LMFVv8WirHL6M4mHcUg@mail.gmail.com \
--to=kernelfans@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.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=piliu@redhat.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