From: osalvador <osalvador@suse.com>
To: Michal Hocko <mhocko@kernel.org>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Dan Williams <dan.j.williams@gmail.com>,
Pavel Tatashin <pasha.tatashin@soleen.com>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>,
Stable tree <stable@vger.kernel.org>
Subject: Re: [RFC PATCH] hwpoison, memory_hotplug: allow hwpoisoned pages to be offlined
Date: Thu, 06 Dec 2018 07:43:22 +0100 [thread overview]
Message-ID: <1544078602.3228.3.camel@suse.com> (raw)
In-Reply-To: <20181205165716.GS1286@dhcp22.suse.cz>
> Btw. the way how we drop all the work on the first page that we
> cannot
> isolate is just goofy. Why don't we simply migrate all that we
> already
> have on the list and go on? Something for a followup cleanup though.
Indeed, that is just wrong.
I will try to send a followup cleanup to fix that.
> Debugged-by: Oscar Salvador <osalvador@suse.com>
> Cc: stable
> Signed-off-by: Michal Hocko <mhocko@suse.com>
It has been a fun bug to chase down, thanks for the patch ;-)
Reviewed-by: Oscar Salvador <osalvador@suse.com>
Tested-by: Oscar Salvador <osalvador@suse.com>
next prev parent reply other threads:[~2018-12-06 6:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 10:03 [RFC PATCH] hwpoison, memory_hotplug: allow hwpoisoned pages to be offlined Michal Hocko
2018-12-03 10:03 ` Michal Hocko
2018-12-04 7:21 ` Naoya Horiguchi
2018-12-04 8:48 ` Michal Hocko
2018-12-04 9:11 ` Naoya Horiguchi
2018-12-04 9:35 ` Michal Hocko
2018-12-05 1:14 ` Naoya Horiguchi
2018-12-04 11:22 ` David Hildenbrand
2018-12-04 12:30 ` osalvador
2018-12-05 12:29 ` Michal Hocko
2018-12-05 16:57 ` Michal Hocko
2018-12-05 16:57 ` Michal Hocko
2018-12-06 5:21 ` Naoya Horiguchi
2018-12-06 8:32 ` Michal Hocko
2018-12-06 8:40 ` osalvador
2018-12-06 9:15 ` Naoya Horiguchi
2018-12-06 12:02 ` Michal Hocko
2018-12-06 6:43 ` osalvador [this message]
2018-12-06 9:02 ` David Hildenbrand
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=1544078602.3228.3.camel@suse.com \
--to=osalvador@suse.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=pasha.tatashin@soleen.com \
--cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.