From: joeyli <jlee@suse.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Michal Hocko <mhocko@kernel.org>, Toshi Kani <toshi.kani@hp.com>,
Jiri Kosina <jkosina@suse.cz>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>,
linux-api@vger.kernel.org
Subject: Re: memory hotplug and force_remove
Date: Wed, 22 Mar 2017 00:13:56 +0800 [thread overview]
Message-ID: <20170321161356.GA20835@linux-l9pv.suse> (raw)
In-Reply-To: <2735706.OR0SQDpVy6@aspire.rjw.lan>
On Mon, Mar 20, 2017 at 10:24:42PM +0100, Rafael J. Wysocki wrote:
> On Monday, March 20, 2017 03:29:39 PM Michal Hocko wrote:
> > Hi Rafael,
>
> Hi,
>
> > we have been chasing the following BUG() triggering during the memory
> > hotremove (remove_memory):
> > ret = walk_memory_range(PFN_DOWN(start), PFN_UP(start + size - 1), NULL,
> > check_memblock_offlined_cb);
> > if (ret)
> > BUG();
> >
> > and it took a while to learn that the issue is caused by
> > /sys/firmware/acpi/hotplug/force_remove being enabled. I was really
> > surprised to see such an option because at least for the memory hotplug
> > it cannot work at all. Memory hotplug fails when the memory is still
> > in use. Even if we do not BUG() here enforcing the hotplug operation
> > will lead to problematic behavior later like crash or a silent memory
> > corruption if the memory gets onlined back and reused by somebody else.
> >
> > I am wondering what was the motivation for introducing this behavior and
> > whether there is a way to disallow it for memory hotplug. Or maybe drop
> > it completely. What would break in such a case?
>
> Honestly, I don't remember from the top of my head and I haven't looked at
> that code for several months.
>
> I need some time to recall that.
>
IMHO.
In the second pass offline in acpi_scan_try_to_offline(), when force_remove flag
enabled, it's still run offline on the parent device even there have any child
device offline failed. And it doesn't return the error from acpi_bus_offline() to
caller.
errdev = NULL;
acpi_walk_namespace(ACPI_TYPE_ANY, handle, ACPI_UINT32_MAX,
NULL, acpi_bus_offline, (void *)true,
(void **)&errdev);
if (!errdev || acpi_force_hot_remove)
acpi_bus_offline(handle, 0, (void *)true,
(void **)&errdev);
In this situation, the parent device or any child device may not really
offline successfully. But acpi_scan_hot_remove, the caller doesn't know that.
Then it cause the later acpi_bus_trim() process failed.
acpi_bus_trim()
-> handler->detach()
-> acpi_memory_device_remove()
-> remove_memory() -> BUG()
because some memory doesn't really offline.
Thanks a lot!
Joey Lee
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-03-21 16:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 19:29 memory hotplug and force_remove Michal Hocko
2017-03-20 21:24 ` Rafael J. Wysocki
2017-03-21 16:13 ` joeyli [this message]
2017-03-28 7:58 ` Michal Hocko
2017-03-28 15:22 ` Rafael J. Wysocki
2017-03-30 8:47 ` Jiri Kosina
2017-03-30 16:20 ` Michal Hocko
[not found] ` <20170330162031.GE4326-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2017-03-30 16:57 ` joeyli
[not found] ` <20170330165729.GN28365-g7OFGfmEpDh8S/rGE13EwQ@public.gmane.org>
2017-03-30 20:15 ` Rafael J. Wysocki
2017-03-31 0:00 ` joeyli
2017-03-31 8:30 ` Michal Hocko
[not found] ` <20170331083017.GK27098-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2017-03-31 10:49 ` joeyli
[not found] ` <20170331104905.GA28365-g7OFGfmEpDh8S/rGE13EwQ@public.gmane.org>
2017-03-31 10:55 ` Michal Hocko
[not found] ` <20170331105505.GM27098-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2017-03-31 11:55 ` joeyli
2017-03-31 12:02 ` Michal Hocko
[not found] ` <20170331120236.GO27098-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2017-03-31 22:35 ` Rafael J. Wysocki
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=20170321161356.GA20835@linux-l9pv.suse \
--to=jlee@suse.com \
--cc=jkosina@suse.cz \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=toshi.kani@hp.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;
as well as URLs for NNTP newsgroup(s).